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
Once the CLI is finished what it's doing (or errors), the python process should exit.
Actual Behavior:
There is a small chance that it will instead just hang. It refuses to respond to ^C and requires a Ctrl+Pause (windows equiv of a SIGKILL) which unfortunately means the stack trace is not printed.
Steps to reproduce:
I have yet to work out a way to reliably reproduce it.
System information:
Operating System: Windows 10 Enterprise
PROS Version: Observed on both 3.1.2 and 3.1.4
Additional Information
I believe this may also be the cause of the errors popping up around the place about JSON decode errors as if atom spawns a prosv5 instance that never closes, it will have a open('compile_commands.json', 'w') locked meaning that a subsequent attempt to read compile_commands.json will have it appear an empty file. This is speculation though (I remember fixing this error for someone by having them restart atom, which adds to my suspicion this is the case though).
The text was updated successfully, but these errors were encountered:
Expected Behavior:
Once the CLI is finished what it's doing (or errors), the python process should exit.
Actual Behavior:
There is a small chance that it will instead just hang. It refuses to respond to ^C and requires a Ctrl+Pause (windows equiv of a SIGKILL) which unfortunately means the stack trace is not printed.
Steps to reproduce:
I have yet to work out a way to reliably reproduce it.
System information:
Operating System: Windows 10 Enterprise
PROS Version: Observed on both 3.1.2 and 3.1.4
Additional Information
I believe this may also be the cause of the errors popping up around the place about JSON decode errors as if atom spawns a prosv5 instance that never closes, it will have a
open('compile_commands.json', 'w')
locked meaning that a subsequent attempt to readcompile_commands.json
will have it appear an empty file. This is speculation though (I remember fixing this error for someone by having them restart atom, which adds to my suspicion this is the case though).The text was updated successfully, but these errors were encountered: