Skip to content

GOL-420: capture correlated WASI HTTP lifecycle traces - #136

Draft
noise64 wants to merge 9 commits into
mainfrom
gol-420-http-transport-instrumentation
Draft

GOL-420: capture correlated WASI HTTP lifecycle traces#136
noise64 wants to merge 9 commits into
mainfrom
gol-420-http-transport-instrumentation

Conversation

@noise64

@noise64 noise64 commented Aug 29, 2026

Copy link
Copy Markdown
Contributor
  • resolves https://linear.app/golem-cloud/issue/GOL-420
  • adds fixed-size, lock-free P2/P3 outgoing HTTP lifecycle journals to the runtime test host
  • folds server connection ownership, response byte accounting, terminal/error/drop boundaries, and overlap diagnostics into the same test-only trace
  • records client and server observations independently without injecting private correlation headers or mutating guest-visible requests
  • attaches decoded journals and existing Wasmtime HTTP warnings only after an invocation fails
  • preserves stock and Golem Wasmtime dispatch semantics, including P2 body-completion ownership
  • remains diagnostic-only: no retry, serialization, timeout inflation, localhost branch, or production behavior change is included
  • keeps GOL-405 separate unless evidence identifies the same behavioral owner

Validation covers 21 focused lifecycle cases in both P2 and P3, guest-header preservation, socket ownership and byte accounting, formatting, and the inherited P3 stream-lifecycle regressions at exact SHA be7547cfcca106f61868e589661fdd1ed9b73ba7.

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