-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validation Receipts Scenario #83
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! I do have a few questions about this one but I'm open to any responses and I'd be happy that this adds great value as it is :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks awesome!
RESOLVES #44
Hehe ^^ I thought this graph was a little too awesome. It turns out it was breaking out of the loop early if it hadn't received any receipts at all yet. With that fixed, I'm seeing much more expected 3 to 6 second timing on this.
Graph now split by op type in "wait_for_complete" mode:
New graph in "no_wait_for_complete" mode... much weirder graph that stops getting data part way through. I assume that is because a bunch of the actions never actually complete, especially as it goes on. But that can be something to figure out in another story: