Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI Failing To Close #83

Closed
Bottersnike opened this issue Feb 26, 2019 · 0 comments
Closed

CLI Failing To Close #83

Bottersnike opened this issue Feb 26, 2019 · 0 comments
Labels
needs reproduction The cause of this issue is still unknown, and/or the issue has not yet been reliably reproduced

Comments

@Bottersnike
Copy link
Contributor

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 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).

@HotelCalifornia HotelCalifornia added the needs reproduction The cause of this issue is still unknown, and/or the issue has not yet been reliably reproduced label Mar 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs reproduction The cause of this issue is still unknown, and/or the issue has not yet been reliably reproduced
Projects
None yet
Development

No branches or pull requests

3 participants