Discard packets statically known to fail #370
Conversation
| /// This is a simple sanity check so the leader can discard transactions | ||
| /// which are statically known to exceed the compute budget, and will | ||
| /// result in no useful state-change. | ||
| pub fn compute_unit_limit_above_static_builtins(&self) -> bool { |
There was a problem hiding this comment.
This could be part of ImmutableDeserializedPacket::new() -> Result, can drop packet there if not enough cu limit. Just to clarify that it is standalone function to support scheduler_controller?
There was a problem hiding this comment.
made it a separate function more just more easily document the behavior and use in filter call.
also didn't want to put it directly in new so we don't need to change any of the existing tests.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #370 +/- ##
=========================================
- Coverage 81.9% 81.8% -0.1%
=========================================
Files 838 838
Lines 227368 227389 +21
=========================================
- Hits 186238 186226 -12
- Misses 41130 41163 +33 |
apfitzge
added
automerge
|
Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. |
|
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
* Discard packets statically known to fail * add test (cherry picked from commit 5f16932) # Conflicts: # core/src/banking_stage/transaction_scheduler/scheduler_controller.rs
* Discard packets statically known to fail * add test (cherry picked from commit 5f16932) # Conflicts: # core/src/banking_stage/transaction_scheduler/scheduler_controller.rs
) * Discard packets statically known to fail (#370) * Discard packets statically known to fail * add test (cherry picked from commit 5f16932) # Conflicts: # core/src/banking_stage/transaction_scheduler/scheduler_controller.rs * resolve conflict --------- Co-authored-by: Andrew Fitzgerald <[email protected]>
) * Discard packets statically known to fail (#370) * Discard packets statically known to fail * add test (cherry picked from commit 5f16932) # Conflicts: # core/src/banking_stage/transaction_scheduler/scheduler_controller.rs * resolve conflicts: old metrics update style --------- Co-authored-by: Andrew Fitzgerald <[email protected]>
…#370) (anza-xyz#375) * Discard packets statically known to fail (anza-xyz#370) * Discard packets statically known to fail * add test (cherry picked from commit 5f16932) # Conflicts: # core/src/banking_stage/transaction_scheduler/scheduler_controller.rs * resolve conflicts: old metrics update style --------- Co-authored-by: Andrew Fitzgerald <[email protected]>
Problem
Summary of Changes
Fixes #