Skip to content

Preserve P4 state in multi-hook request chains - #5

Draft
xylophonez wants to merge 1 commit into
review-base/hb-edge-20260810from
fix/p4-multi-hook-edge
Draft

xylophonez wants to merge 1 commit into
review-base/hb-edge-20260810from
fix/p4-multi-hook-edge

Conversation

@xylophonez

@xylophonez xylophonez commented Aug 10, 2026

Copy link
Copy Markdown
Owner

Preserves fields already carried by the P4 request hook and selects the P4 handler from a multi-hook request chain by its ledger-device. Includes a real-node regression that places P4 between pass-through and observer hooks.

Scope: one existing device file; no dev_meta changes.

Validation: rebar3 device test -m dev_p4 — 4/4 passed. The repository-wide suite is currently blocked on current edge by the unchanged hb_beamr native driver failing with open_error -10.

@xylophonez
xylophonez force-pushed the fix/p4-multi-hook-edge branch from 92e38cc to de30921 Compare August 10, 2026 14:15
@xylophonez
xylophonez changed the base branch from review-base/hb-7135fd to review-base/hb-edge-20260810 August 10, 2026 14:15
@xylophonez
xylophonez force-pushed the fix/p4-multi-hook-edge branch 3 times, most recently from 80be3ea to 17584d4 Compare August 10, 2026 14:23
… hooks

request/3 returned a fresh map on every success path, dropping any fields
carried on the hook request. A handler ordered after p4 then receives an
incomplete request and may resolve against the wrong target.

balance/3 matched a single handler from hb_hook:find, so /~p4@1.0/balance
returned 500 on any node with more than one request hook. It now selects the
p4 handler from the list by its ledger-device.
@xylophonez
xylophonez force-pushed the fix/p4-multi-hook-edge branch from 17584d4 to e958625 Compare August 10, 2026 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant