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
I reproduced this on v0.23.0 source, but not on current 0.24.0 source. In my case it depends on terminal color detection, not whether the missing branch is named main.
Using Linux x86_64, Bun 1.4.2, each revision's frozen dependencies, clean per-case HOME/config and an isolated PTY:
hunk diff HUNK1193_MISSING_BRANCH..HEAD
Source revision
PTY result
v0.23.0, 7991d3034af1d2116e9c77db31265e409a73bd9f
Prints the reported revision error, then remains alive until my 5s test deadline
main / 0.24.0, a0e3cf536ef941f6bdff928113a19006af023ce8
Prints the same error and exits 1 in about 0.13s
Additional checks:
v0.23.0 still hangs with --no-extensions, and with explicit --theme auto or --theme terminal.
--theme github-dark avoids the hang on v0.23.0 in the same PTY (exit 1 in about 0.12s).
Current source exits 1 with all three explicit themes too; auto/terminal take about 0.28–0.29s.
Both revisions exit 1 normally when run with pipes rather than a PTY. --help exits 0 on both with either setup; the valid HEAD..HEAD pipe control exits 0.
The old PTY output includes the terminal color queries. The existing detectTerminalColors cleanup change in #1130 restores paused stdin when it wasn't previously flowing, with a comment specifically covering startup failure before a renderer takes ownership. That is consistent with this result; I haven't bisected the exact release boundary or tested a new patch.
These were source launches, not the installed/Homebrew/compiled binary. The test PTY did not answer the color queries, so this covers the timeout path rather than a particular terminal emulator's responses. Could you share hunk --version, installation method, terminal/OS and configured theme—and whether it still happens after updating to 0.24.0?
This comment was generated by Pi using GPT-6.1 Sol
Activity
squad-joey commentedon Oct 19, 2026
I reproduced this on v0.23.0 source, but not on current 0.24.0 source. In my case it depends on terminal color detection, not whether the missing branch is named
main.Using Linux x86_64, Bun 1.4.2, each revision's frozen dependencies, clean per-case HOME/config and an isolated PTY:
7991d3034af1d2116e9c77db31265e409a73bd9fa0e3cf536ef941f6bdff928113a19006af023ce8Additional checks:
--no-extensions, and with explicit--theme autoor--theme terminal.--theme github-darkavoids the hang on v0.23.0 in the same PTY (exit 1 in about 0.12s).--helpexits 0 on both with either setup; the validHEAD..HEADpipe control exits 0.The old PTY output includes the terminal color queries. The existing
detectTerminalColorscleanup change in #1130 restores paused stdin when it wasn't previously flowing, with a comment specifically covering startup failure before a renderer takes ownership. That is consistent with this result; I haven't bisected the exact release boundary or tested a new patch.These were source launches, not the installed/Homebrew/compiled binary. The test PTY did not answer the color queries, so this covers the timeout path rather than a particular terminal emulator's responses. Could you share
hunk --version, installation method, terminal/OS and configured theme—and whether it still happens after updating to 0.24.0?This comment was generated by Pi using GPT-6.1 Sol