-
Notifications
You must be signed in to change notification settings - Fork 69
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
[occ] Add struct field and helpers for estimate prefills #341
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## occ-main #341 +/- ##
============================================
- Coverage 56.09% 56.09% -0.01%
============================================
Files 627 627
Lines 52759 52773 +14
============================================
+ Hits 29597 29604 +7
- Misses 21060 21065 +5
- Partials 2102 2104 +2
|
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.
Assuming -1 for incarnation is okay, this looks good to me.
types/tx_batch.go
Outdated
|
||
// DeliverTxEntry represents an individual transaction's request within a batch. | ||
// This can be extended to include tx-level tracing or metadata | ||
type DeliverTxEntry struct { | ||
Request abci.RequestDeliverTx | ||
Request abci.RequestDeliverTx | ||
Metadata DeliverTxMetadata |
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.
2 cents: I'd probably would have just put the Writeset here, because Metadata normally means things like headers/trackers/tracers and not as much real-arguments to the function.
tasks/scheduler.go
Outdated
@@ -57,6 +57,7 @@ func (dt *deliverTxTask) Increment() { | |||
|
|||
// Scheduler processes tasks concurrently | |||
type Scheduler interface { | |||
PrefillEstimates(ctx sdk.Context, metadatas []sdk.DeliverTxMetadata) |
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.
2 cents: if this always must happen prior to ProcessAll, it may be worth just including the logic in ProcessAll to simplify the interaction.
…ield to be more descriptive of function
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
## Describe your changes and provide context This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch ## Testing performed to validate your change Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled
Describe your changes and provide context
This adds in the ability to prefill estimates based on metadata passed along with deliverTxBatch
Testing performed to validate your change
Unit Test to verify that multiversion store initialization is now idempotent, and works properly regardless of whether estimate prefill is enabled