Skip to content

fix: track cancelled calls and late results - #210

Merged
kerlenton merged 2 commits into
kerlenton:mainfrom
Guflly:fix/cancelled-call-state
Aug 7, 2026
Merged

fix: track cancelled calls and late results#210
kerlenton merged 2 commits into
kerlenton:mainfrom
Guflly:fix/cancelled-call-state

Conversation

@Guflly

@Guflly Guflly commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

What and why

Cancelled calls currently look successful, while a later conforming response looks hung. This records cancellation separately, preserves late results as observations, and carries those states through JSON, text, HTML, HAR, and OTLP exports.

The TUI shows cancel and late rows and filters, and check can opt into failing on late results with --fail-on late-result.

Fixes #198

Focused store, exporter, TUI, and CLI tests pass, along with go vet ./.... The full Windows run still hits existing Unix-only fixtures and filesystem assumptions.

Checklist

  • make check passes (gofmt, vet, staticcheck, race tests)
  • Added or updated tests for the change, where it makes sense
  • Updated the README / docs if user-facing behaviour changed

@github-actions github-actions Bot added the fix label Aug 2, 2026
@Guflly
Guflly force-pushed the fix/cancelled-call-state branch from 4087f9e to 3e7b0c5 Compare August 2, 2026 18:42
@Guflly
Guflly force-pushed the fix/cancelled-call-state branch from 3e7b0c5 to bd87ef0 Compare August 7, 2026 13:58
@kerlenton

Copy link
Copy Markdown
Owner

Thank you!

@kerlenton
kerlenton merged commit 5979359 into kerlenton:main Aug 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A cancelled call reads as a clean success, and a conforming cancellation reads as a hung request

2 participants