Skip to content

fix(spawn): enter treehouse slot with --no-fetch to avoid 60s isolation timeout - #18

Merged
jorguez96 merged 2 commits into
mainfrom
fm/fm-spawn-treehouse-isolation
Sep 25, 2026
Merged

jorguez96 merged 2 commits into
mainfrom
fm/fm-spawn-treehouse-isolation

Conversation

@jorguez96

Copy link
Copy Markdown
Owner

Isolated-copy fix: enter the treehouse slot with --no-fetch so spawn setup stops tripping the 60s isolation timeout. Regression test included (tests/fm-spawn-treehouse-no-fetch.test.sh); lint clean, no-fetch/settle/freshen suites green. Rebased onto current main.

…on timeout

treehouse get fetches origin before entering the subshell, and fantasy-strategy proves that fetch exceeds the 60s entry window while the pane still reports the spawning project. freshen_spawn_worktree_base already owns base freshness after entry, so skip the pre-entry fetch.

Reproduced live on herdr: bare get stuck at Setting up worktree with foreground_cwd frozen, --no-fetch entered slot 2 in under 5s. Adds fm-spawn-treehouse-no-fetch regression test.
@jorguez96
jorguez96 force-pushed the fm/fm-spawn-treehouse-isolation branch from 2c47af5 to 8459229 Compare September 24, 2026 23:44
Remove the fork's Require no-mistakes workflow and its CONTRIBUTING requirement so direct-PR delivery is accepted.
Pin CI treehouse to v2.3.0, the first line with get --no-fetch, which the spawn entry needs to avoid the 60s isolation timeout.
Update the tangle-guard expectation to the no-fetch entry command.
@jorguez96
jorguez96 merged commit 57e978e into main Sep 25, 2026
13 checks passed
jorguez96 pushed a commit that referenced this pull request Sep 25, 2026
Merge origin/main into the 251-commit upstream reconciliation.
Keeps the landed #18 content where they overlap: the treehouse
--no-fetch spawn entry, the v2.3.0 pin, the tangle-guard expectation,
the CONTRIBUTING direct-PR wording, and the no-mistakes-required
workflow removal (upstream's later edits to that workflow are dropped
with the file, per the fork's direct-PR posture).
Upstream-synced content is otherwise untouched.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants