Skip to content

fix(internode): release rejected incoming packages - #714

Merged
wolfy-j merged 1 commit into
mainfrom
fix/internode-rejected-delivery-release
Sep 10, 2026
Merged

wolfy-j merged 1 commit into
mainfrom
fix/internode-rejected-delivery-release

Conversation

@wolfy-j

@wolfy-j wolfy-j commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

A decoded internode package remained owned by the service when local delivery rejected it, but the error path did not release it. Packages carrying bounded-retention leases could therefore leak their payload reservations. Successful delivery already transfers ownership to the receiver and remains unchanged.\n\nThe service now releases a decoded package exactly when the delivery callback returns an error, and the existing callback type documents that transactional ownership rule.\n\nRegression coverage uses an observable retention lease to prove both sides:\n- rejection releases the package and lease exactly once;\n- acceptance does not release early and transfers ownership to the receiver.\n\nValidation:\n- focused ownership regression passes 100 times under race;\n- full cluster/internode race suite passes;\n- pinned golangci-lint v2.13.2 reports 0 issues.\n\nThe rebased PR contains only the internode ownership fix and its regression test. Unrelated publish and terminal test adjustments were removed. It adds no new exported API or signature, runtime/Lua/native binding, config or protocol field, wire change, lifecycle state, documentation, worker, or timer.

@wolfy-j
wolfy-j requested a review from skhaz September 9, 2026 21:31
@wolfy-j
wolfy-j force-pushed the fix/internode-rejected-delivery-release branch from a5b0537 to fbdb428 Compare September 10, 2026 01:55
@wolfy-j
wolfy-j force-pushed the fix/internode-rejected-delivery-release branch from fbdb428 to 70c7737 Compare September 10, 2026 02:07
@wolfy-j
wolfy-j merged commit d78a66c into main Sep 10, 2026
9 checks passed
@wolfy-j
wolfy-j deleted the fix/internode-rejected-delivery-release branch September 10, 2026 02:26
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.

2 participants