-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Make python venv creation independent from the user #4189
Conversation
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.
Nice catch! 👀
I did quite a bit of testing on this and unfortunately the change as proposed so far does not work. The problem is that semaphore creation is subject to the processes A complete fix should still be possible by wrapping all the venv creation steps in an extra python subprocess (which would be single threaded) and use that to manage the inter process synchronization. This would have the nice side effect of securing the sync against SIGKILLs, SEGFAULTS, and the like. |
There's also the option of creating separate cache directories per user. |
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.
Thanks for the fix!
A permission error caused python operator to fail when it was previously used by another system user with the same set of requirements.