Repository navigation
fix: share one project-list build across callers; log slow builds - #36
Merged
Merged
Conversation
The deck abandons a project list after 150s and asks again on its next refresh, but the walk in the main process keeps going, so each retry stacked another full walk (58 repos of git, ~15.7k Codex rollout heads) on the first. Right after a boot SIHYEONG-4080 logged five 150s timeouts in a row (2026-10-12). Late callers now join the build under way, and a build slower than 20s is logged with its time summed per stage. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AwhRmzUt3nLnhqU1NJyzpW
writingdeveloper
added a commit
that referenced
this pull request
Oct 15, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AwhRmzUt3nLnhqU1NJyzpW
Merged
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
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.
Problem
After 150s the deck stops waiting for a project list and asks again on its next refresh. The walk already running in the main process does not stop, so each retry started another full walk on top of it: 58 repositories of git, plus about 15.7k Codex rollout heads on SIHYEONG-4080. Right after a boot this showed up as five 150s timeouts in a row (2026-10-12, devdeck.log).
Change
projects:listkeeps one build in flight. Any caller that arrives while it runs, local or over Link, receives that same promise.warn, with time summed per stage (scan,git,sessions,cue). After the next slow boot, the log will show which stage was slow.QA
npm test: 1268 passed, 1 skipped. New test: a second call during a build returns the same promise, and a call after it lands builds fresh.🤖 Generated with Claude Code
https://claude.ai/code/session_01AwhRmzUt3nLnhqU1NJyzpW