docs(#518/#519/#520): case study — the trace that couldn't name its socket - #528
Merged
Conversation
…ocket The measure-fix-measure narrative behind PRs #524/#525/#526: one scripted js-attach scenario against the real server, run byte-for-byte identically before and after the fixes, with the artifact diffs as the acceptance test. Baseline reproduced all three filings on Windows (111 futile threads polls ending in a false warning; 0 routing lines in the per-session log vs 905 in an undocumented per-pid file; 0 of 348 trace records naming their connection); the after run measured 4 threads frames, 520 routing lines in the session log, success flags on response lines, and 129 of 129 records tagged parent/child. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017Qu6eqpquEZ5rdXHV5s7QA
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The measure-fix-measure narrative behind the #518/#519/#520 observability cluster (PRs #524/#525/#526): one scripted js-attach scenario against the real server — idle
node --inspecttarget,DAP_TRACE=1, attach → 14s wait → pause → stack → failing evaluate — run byte-for-byte identically before and after the fixes, with the artifact diffs as the acceptance test.threadsframes in the attach traceproxy-<sessionId>.logsuccessflag anywheresuccess: false, request_seq: …parent/child:<id8>)Adds the case study under
docs/case-studies/and one README line, following the #523 pattern.Dogfood side-finding filed during the capture: #527 (dev-proxy can't inject backend env vars).
🤖 Generated with Claude Code
https://claude.ai/code/session_017Qu6eqpquEZ5rdXHV5s7QA