-
Notifications
You must be signed in to change notification settings - Fork 290
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
Orchestrator refactor #512
Orchestrator refactor #512
Conversation
* cosmetics * better waiting for e2e orchestrator * use require instead of assert in some qgb e2e places * restore the confirm check * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go * Update e2e/qgb/orchestrator_test.go
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.
some minor nits, but overall a big 👍
probably about as clean as we're going to get! anything smaller and I think we're treading into over abstraction
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.
Questions :D
// FIXME sdktypestx.BroadcastMode_BROADCAST_MODE_BLOCK waits for a block to be minted containing | ||
// the transaction to continue. This makes the orchestrator slow to catchup. | ||
// It would be better to just send the transaction. Then, another job would keep an eye | ||
// if the transaction was included. If not, retry it. But this would mean we should increment ourselves | ||
// the sequence number after each broadcasted transaction. | ||
// We can also use BroadcastMode_BROADCAST_MODE_SYNC but it will also fail due to a non incremented | ||
// sequence number. |
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.
@evan-forbes please when you have time, let me know what you think about this,
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.
we might want to create larger txs with many sdk.Messages and still use broadcast mode sync just for simplicity, but I can definitely see where a more async approach would be desirable
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.
Should we create an issue for that?
@evan-forbes ready for final review, after you're back. Also, please check the comments up. |
Codecov Report
@@ Coverage Diff @@
## qgb-integration #512 +/- ##
===================================================
+ Coverage 11.72% 12.70% +0.97%
===================================================
Files 65 56 -9
Lines 10881 9548 -1333
===================================================
- Hits 1276 1213 -63
+ Misses 9515 8252 -1263
+ Partials 90 83 -7
Continue to review full report at Codecov.
|
merging :D |
No description provided.