[consensus/marshal] Abstract over consensus engine#3253
[consensus/marshal] Abstract over consensus engine#3253clabby wants to merge 7 commits intocl/minimmitfrom
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
commonware-mcp | beedef7 | Mar 06 2026, 07:35 PM |
83566aa to
a338863
Compare
Deploying monorepo with
|
| Latest commit: |
beedef7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3e35ac7d.monorepo-eu0.pages.dev |
| Branch Preview URL: | https://cl-marshal-minimmit.monorepo-eu0.pages.dev |
a338863 to
a7fe073
Compare
e7e4a5d to
19d42bb
Compare
a7fe073 to
3d69781
Compare
98e2327 to
ee361c6
Compare
ee361c6 to
e3a104d
Compare
e3a104d to
a8ebe9d
Compare
a8ebe9d to
f183337
Compare
fbb0dc2 to
88eaa68
Compare
9f92d1a to
b16d80e
Compare
b16d80e to
f03d1d2
Compare
e326c6b to
96f0d48
Compare
30c6dd8 to
96550d9
Compare
96550d9 to
556fb37
Compare
4322390 to
a091929
Compare
Codecov Report❌ Patch coverage is @@ Coverage Diff @@
## cl/minimmit #3253 +/- ##
===============================================
- Coverage 93.87% 93.78% -0.09%
===============================================
Files 440 440
Lines 149871 147847 -2024
===============================================
- Hits 140694 138663 -2031
- Misses 9177 9184 +7
... and 30 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
a091929 to
f9e1fbd
Compare
| ["commonware_consensus::marshal::resolver::handler::tests::conformance::CodecConformance<Request<D>>"] | ||
| n_cases = 65536 | ||
| hash = "481cd68f2e6452c0dda512c75d74ddd2e19ac6c9fb19c642c1a152a0d830c1b2" | ||
| hash = "a87609f8692a7d2208a327d37bdabc7329567b15a5745f3947760a7fd383cbe2" |
There was a problem hiding this comment.
I was a bit torn about this, but after thinking about it a bit more, I believe this is safe to roll out incrementally. The resolver does not block peers on decode failure, and notarized block backfill is a secondary path in marshal. Finalized block backfill is unchanged.
While a network is rolling out their upgrades to this version, Notarized requests between mixed versions will fail and retry. The fetcher will eventually select a same version peer that can complete their request or cancel the request once a finalized block is processed at a higher view.
We could add in some more complex machinery that allows for nodes to understand the old Notarized(Round) request as well as the new Notarized(Round, Commitment) request temporarily, but it isn't necessary given that the penalty is slightly degraded notarized request availability for a temporary period of time.
There was a problem hiding this comment.
The resolver does not block peers on decode failure
It does to my knowledge?
There was a problem hiding this comment.
In main, it skips:
monorepo/resolver/src/p2p/engine.rs
Lines 350 to 357 in 18fdce5
(Note that we did not change the response payload, which would trigger a block. We just changed the key for the Notarized test type.)
2285b64 to
83c6970
Compare
83c6970 to
40eae04
Compare
resolve conflict: apply peer_provider rename to moved harness file
40eae04 to
beedef7
Compare
Overview
Note
Do not merge. Stacked on top of #2884
Abstracts
marshalover consensus engine variants.