You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6551112
Browse filesBrowse the repository at this point in the historyBrowse files
fix: bound the stdin wait only for sockets; time-limit the unsent-memory check
Consensus review follow-ups.
- `readRunStdin` applies the 3s first-byte wait only when stdin is a
socket, which is what an agent's shell tool or a Node `spawn` hands a
child. A shell pipeline is a FIFO and is read to EOF as before, so
`dbt build | altimate-code run …` keeps its input however long the
producer takes.
- The exit check for unsent memory is capped at 5s, reports an
unreadable local count as unknown, and is injectable and tested
(gating, unknown, timeout, unlinked).
- Notice wording: "N memories on this machine are not in the workspace
yet", since the count is the project's, not only this run's.
- A test ties `SIGN_IN_COMMAND`'s `--method` to a label the
`altimate-backend` provider actually has.
- New-file markers; the empty-record comment folded into its docblock.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_011chv9Rmu7jQXokum1WNcs7
/** A socket stdin (unless `file` or `fifo` is set) whose stream yields `chunks` (the first at once, each later one after `delayMs`), then ends unless `open` is set. */
0 commit comments