Skip to content

Bump aznet to the idempotent-WriteRaw fix - #10

Open
Atsika wants to merge 1 commit into
mainfrom
chore/bump-aznet-idempotent-writeraw
Open

Bump aznet to the idempotent-WriteRaw fix#10
Atsika wants to merge 1 commit into
mainfrom
chore/bump-aznet-idempotent-writeraw

Conversation

@Atsika

@Atsika Atsika commented Aug 15, 2026

Copy link
Copy Markdown
Collaborator

Picks up Atsika/aznet#5.

A failed WriteRaw is resent verbatim by aznet's flush(). When the write had actually landed and only its response was lost, the resend duplicated the chunk and desynced the peer's Noise nonce, resetting the tunnel. WriteRaw now carries a core-owned chunk sequence that each driver maps to its native idempotency primitive (azqueue: message header, aztable: row key → 409, azblob: append-position condition → 412), so a resend collides instead of duplicating.

Dependency-only change; no proxyblob source is touched and the aznet driver interface change is internal to aznet.

Verified: go build ./..., go vet ./..., go test ./... -race -count=1, and the wasm agent build all pass against the bumped module (GOWORK=off, so the published version rather than the local checkout).

A failed WriteRaw is resent verbatim by aznet's flush(). When the write had
actually landed and only its response was lost, the resend duplicated the chunk
and desynced the peer's Noise nonce, which reset the tunnel. WriteRaw now
carries a core-owned chunk sequence that each driver maps to its native
idempotency primitive, so a resend collides instead of duplicating.

Dependency-only change: no proxyblob source touched, and the driver interface
change is internal to aznet.
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