Diagnostic: print PWD before nvm install#31
Draft
mokagio wants to merge 3 commits into
Draft
Conversation
Capture the PWD nvm walks on the explicit-version Windows path, to settle whether PR #24's normalization actually yields a forward-slash $PWD that nvm_find_project_dir sees. Printed to stderr so it flushes before the hang swallows block-buffered stdout. `one-trim` equal to `PWD` proves the backslash `${PWD%/*}` no-op loop; a shorter `one-trim` means normalization stuck and the hang is elsewhere. --- Generated with the help of Claude Code, https://claude.com/claude-code Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Build 118 showed buffered hook output never flushes while the job hangs —
even the stdout echo before the diag was swallowed. So don't hang: print
the PWD, the one-step `${PWD%/*}` trim, and a verdict on whether the trim
is a no-op (the backslash loop), then `return` before the real install.
The hook exits, Buildkite flushes the log, and the job ends instead of
hanging. Node won't install, so the verify command fails — expected; the
`[diag]` lines are the payload.
---
Generated with the help of Claude Code, https://claude.com/claude-code
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Build 119 froze before the v2 diag, so the hang is at normalization or
`source nvm.sh`, not `nvm install`. Bisect it: capture PWD before and
after normalization, then source nvm, with a buffer-filling padding flush
BEFORE each risky step so a later hang can't erase earlier readings. The
last `[diag] STAGE` line in the log pinpoints where it hangs, and the
`trim-noop` flags show whether `${PWD%/*}` is the backslash no-op.
---
Generated with the help of Claude Code, https://claude.com/claude-code
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Diagnostic (not for merge)
Settles the one open question: does PR #24's normalization actually give nvm a forward-slash
$PWDon the explicit-version Windows path? The explicit jobs hang innvm_find_project_dir, whose${path_%/*}loop never terminates on a pure-backslash PWD.Prints
$PWD,pwd, and${PWD%/*}to stderr (so it flushes before the hang swallows block-buffered stdout) right beforenvm install. Read on the hungv20.19.5/v24.15.0Windows jobs:one-trimequalsPWD→ backslash no-op loop; normalization didn't stick → fix normalization.one-trimshorter thanPWD→ forward-slash; normalization stuck → the hang is elsewhere.🤖 Generated with Claude Code