apollo_consensus_orchestrator: tmp dirty tests for SNIP-35 (NOT FOR MERGE)#13857
Conversation
5d2a6e1 to
459b6ed
Compare
a212b4d to
29bdf7a
Compare
459b6ed to
1e777d3
Compare
29bdf7a to
6afda0a
Compare
1e777d3 to
ab50113
Compare
48944e0 to
cafe0b9
Compare
ab50113 to
2519789
Compare
cafe0b9 to
c4353ed
Compare
2519789 to
1bb7454
Compare
c4353ed to
e6ed317
Compare
1bb7454 to
a515840
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9fd2bd9. Configure here.
| //! - security (overflow, extreme inputs, proposer-validator symmetry) | ||
| //! - mixed-node scenarios (pre-SNIP-35 nodes producing fee_proposal=0) | ||
| //! - sharp price changes (oracle spikes, crashes, recoveries) | ||
|
|
There was a problem hiding this comment.
Explicitly "NOT FOR MERGE" test files committed
Medium Severity
Both new test files carry explicit "NOT FOR MERGE" declarations in their module-level doc comments (snip35_stress_test.rs line 3: "These tests are NOT intended to be merged", snip35_integration_test.rs line 3: "NOT FOR MERGE"), and the PR title repeats this. Nevertheless, both are wired into the build via #[cfg(test)] mod declarations in fee_market/mod.rs and lib.rs. While the #[cfg(test)] gate prevents production impact, these files — along with their module registrations — would land in the main branch if this PR were merged.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 9fd2bd9. Configure here.



No description provided.