-
Notifications
You must be signed in to change notification settings - Fork 2.9k
perf(core): cut runtime sync I/O on tool hot path by 91% #3581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e48dcc4
perf(core): make chat recording writes async
8fa7f4c
perf(core): cache repeated fs lookups on tool hot path
d648596
test(core): cache reset hooks + regression-guards from audit
341b90c
fix(core): cache chatsDirEnsured only on mkdir success
bf24fff
fix(cli): destroy stdout instead of process.exit on EPIPE
869a4e3
fix(cli): bound runExitCleanup with per-fn + wall-clock timeouts
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
flush()only runs on the graceful path; the EPIPE exit path now silently drops queued records.This line correctly drains the queue on
Config.shutdown(), butnonInteractiveCli.ts:181still callsprocess.exit(0)directly when stdout gets EPIPE — bypassingrunExitCleanupentirely, soflush()never runs and queued records are lost.Under sync writes this was harmless: bytes were on disk before the syscall returned, regardless of how the process exited. After this PR, the same code path becomes silent data loss.
Trigger case:
qwen -p "list every file in this repo" | head -1.headexits → EPIPE on stdout →process.exit(0)→ ~5 queued records (the most recent assistant turn + tool results) silently lost. This is a routine CLI usage pattern —cli | head,cli | less,cli | grep -m 1— not an edge case.Fix: at minimum, change
nonInteractiveCli.ts:181fromprocess.exit(0)toprocess.stdout.destroy(), so the naturalfinally→runExitCleanupchain can complete the flush. Claude Code'sprocess.tsuses exactly this pattern —stream.destroy()on EPIPE without exiting — for the same reason.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in bf24fff at
nonInteractiveCli.ts:181—process.exit(0)→process.stdout.destroy(), with a regression test that emits EPIPE mid-stream and assertsstdout.destroyis called (mockedprocess.exitwould throw if the bypass came back).One subtlety from implementing it: I tried adding
abortController.abort()alongside the destroy, but the abort path runshandleCancellationErrorwhich itself callsprocess.exit(130)— same bypass on a different code path. So the handler now only destroys stdout and lets the natural function return drive cleanup. Token waste on EPIPE is bounded by the in-flight LLM response and seems like the right trade vs. data loss.