-
Notifications
You must be signed in to change notification settings - Fork 130
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
Refactored locking implementation. #2084
Conversation
eee5cec
to
9a7e0cc
Compare
Rebased after #2068 |
We have refactored the locking implementation in the worker as a self-contained package "packages/openlock". The package is also available on github https://github.com/vdbergh/openlock and on PyPi https://pypi.org/search/?q=openlock This PR cleans up the worker code considerably.
https://stackoverflow.com/questions/48571212/why-is-sys-exit-causing-a-traceback *** Another worker (with PID=3424) is already running in this directory ***
Traceback (most recent call last):
File "C:\Users\WDAGUtilityAccount\Desktop\worker\worker.py", line 1625, in <module>
sys.exit(worker())
SystemExit: 1 |
Is there any particular reason why on Windows Python is invoked as |
The worker is started with a double click on a launcher cmd, with the -i the user views the traceback in case of error, otherwise the windows simply close. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested successfully on:
- linux
- windows wsl2
- windows 10/11 msys2 bash
- windows 10/11 msys2 cmd
Triggered the worker updated, thank you @vdbergh |
We have refactored the locking implementation in the worker as a self-contained package "packages/openlock". The package is also available on github
https://github.com/vdbergh/openlock
and on PyPi
https://pypi.org/search/?q=openlock
This PR cleans up the worker code considerably.