Repository navigation
v0.11.0-rc6
Pre-release
Pre-release
·
68 commits
to develop
since this release
π What's New
- INC-129 root cause fixed:
l1-info-tree-indexfallback used the wrong tree's index (#1794, closes #1795): the fallback ingetFirstL1InfoTreeIndexForL1Bridgetookroot.IndexfrombridgeL1.GetLastRootβ a position in the L1 bridge exit tree (a deposit count, ~1,146,035) β and passed it tol1InfoTree.GetInfoByIndex, which queriesSELECT * FROM l1info_leaf WHERE position = $1, an L1 info tree index. Two different trees, two different counters, both bareuint32. The row could not exist, soGET /bridge/v1/l1-info-tree-indexreturned HTTP 500sql: no rows in result setwhenever the L1 bridge syncer trailed the L1 info tree syncer. The fallback now callsGetLatestL1InfoLeafUntilBlock(ctx, root.BlockNum), clamping to the most recent info-tree leaf at or before the last block the bridge syncer indexed β the clamp the original code intended, in the correct index space. The tip-anchored binary search, theGetRootByLERjoin, andErrNotOnL1Infoare all retained. - Same bug fixed in
autoclaim(#1794, closes #1795):autoclaim/proof/preparer.gocarried a verbatim copy of the index-space confusion in its ownGetRootByLERfallback. It now clamps onroot.BlockNumtoo. - Cross-syncer error taxonomy (#1794): endpoints that join syncers which can sit at different heights now distinguish "not indexed yet" from a genuine fault, via a shared
httpStatusForSyncerErrorhelper:ErrBlockNotProcessed,l1infotreesync.ErrNotFound,ErrNoBlock0,db.ErrNotFound,ErrNotOnL1Infoβ 404;sync.ErrInconsistentStateβ 503; anything else β 500. Not-ready conditions now log atDebug/Warninstead ofError, so alert volume does not simply migrate from HTTP 500s into ERROR logs. ClaimProofHandlermetrics fix (#1794):statusCodewas initialised to200and never reassigned across all 13 exit paths, so every failure was invisible in metrics. All exits now report the correct status.GetInfoByIndexnot-found is now properly wrapped (#1794):getInfoByIndexWithTxskippeddb.ReturnErrNotFound, returning a rawsql: no rows in result setβ the literal 500 body in INC-129 β leavingerrors.Is(err, db.ErrNotFound)dead code at three call sites.
β οΈ Breaking Changes
- π API/CLI: HTTP 500 β 404 / 503 on three endpoints.
/bridge/v1/l1-info-tree-index,/bridge/v1/claim-proof, and the L1 path of/bridge/v1/injected-l1-info-leafnow return404when a syncer has not indexed the requested data yet (callers should treat it as not ready yet, retry later) and503when a syncer is halted / in an inconsistent state. Previously all of these were500(#1794). /injected-l1-info-leaf's L2 path already returned404; only its L1 path changes.bridgeservice/client:GetL1InfoTreeIndexandGetClaimProofswitch fromdoRequesttodoRequestAllowNotFound, so they now return theErrNotFoundsentinel on404instead of a generic error. Signatures and return types are unchanged, but callers that treated any error as fatal may now want to retry onErrNotFound. A503deliberately stays a plain non-ErrNotFounderror so a halted syncer is not mistaken for "not indexed yet".- No success-path response body or schema changed anywhere.
π Config Updates
- None.
π Bug Fixes
GET /bridge/v1/l1-info-tree-indexno longer returns HTTP 500 when the L1 bridge syncer trails the L1 info tree syncer (#1794).autoclaim'sGetRootByLERfallback no longer mixes L1 bridge exit tree indices with L1 info tree indices, closing #1795.ClaimProofHandlernow reports accurate HTTP status codes in metrics on all 13 exit paths (#1794).GetInfoByIndexnot-found errors are now correctly wrapped asdb.ErrNotFoundinstead of leaking a raw SQL error (#1794).
Full changelog: v0.11.0-rc5...v0.11.0-rc6