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
Tachyon's TUI sometimes does not work on the first try #143040
Hummm, looking at your invocation I am noticing is just wrong. You are calling the profiler with:
sudo -E SAMPLING_LIVE_TRACE=/tmp/live_trace.log ./python.exe -m profiling.sampling run -d 99999 --live -m test test_gc -F SAMPLING_LIVE_TRACE=/tmp/live_trace.log ./python.exe -m profiling.sampling run -d 99999 --live -m test test_gc -F
but that's not how you are supposed to nest them: the second call should NOT use ./python.exe. What's happening here is that the program is failing to even start. Maybe we should make this into "the live TUI doesn't;t properly report starting errors"
It you launch this with sudo -E SAMPLING_LIVE_TRACE=/tmp/live_trace.log ./python.exe -m profiling.sampling run -d 99999 --live -m test test_gc it should work
I have tried sudo -E SAMPLING_LIVE_TRACE=/tmp/live_trace.log ./python.exe -m profiling.sampling run -d 99999 --live -m test test_gc in the exact same environment as you report (macOS + vsCode terminal + zsh) and cannot reproduce
Ok I am 100% sure the problem here is that the program is crashing with an exception or something else before it can start. The UX is horrible because the user gets no feedback and you cannot see the exception :(
changed the title [-]Tachion's TUI sometimes does not work on the first try[/-][+]Tachyon's TUI sometimes does not work on the first try[/+]on Dec 26, 2025
Activity
yihong0618 commentedon Dec 21, 2025
it happens to me once, but it happens in VS Code terminal
pablogsal commentedon Dec 21, 2025
Will take a look soon
pablogsal commentedon Dec 21, 2025
@sobolevn can you confirm if this also happens to you in a non-vscode terminal ?
pablogsal commentedon Dec 21, 2025
Also in the video you are nesting two --live instances so that is also a possible cause. Does this happen also if you don't do that?
pablogsal commentedon Dec 21, 2025
Hummm, looking at your invocation I am noticing is just wrong. You are calling the profiler with:
but that's not how you are supposed to nest them: the second call should NOT use
./python.exe. What's happening here is that the program is failing to even start. Maybe we should make this into "the live TUI doesn't;t properly report starting errors"pablogsal commentedon Dec 21, 2025
It you launch this with
sudo -E SAMPLING_LIVE_TRACE=/tmp/live_trace.log ./python.exe -m profiling.sampling run -d 99999 --live -m test test_gcit should workpablogsal commentedon Dec 21, 2025
I have tried
sudo -E SAMPLING_LIVE_TRACE=/tmp/live_trace.log ./python.exe -m profiling.sampling run -d 99999 --live -m test test_gcin the exact same environment as you report (macOS + vsCode terminal + zsh) and cannot reproducepablogsal commentedon Dec 21, 2025
Ok I am 100% sure the problem here is that the program is crashing with an exception or something else before it can start. The UX is horrible because the user gets no feedback and you cannot see the exception :(
[-]Tachion's TUI sometimes does not work on the first try[/-][+]Tachyon's TUI sometimes does not work on the first try[/+]gh-143040: Exit taychon live mode gracefully and display profiled scr…
pablogsal commentedon Dec 27, 2025
Closing as now we have a better error message
pythongh-143040: Exit taychon live mode gracefully and display profil…