-
Notifications
You must be signed in to change notification settings - Fork 16
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
Possible concurrency issues with resolve on a cluster #19
Comments
Yeah makes sense. |
Oh, by the way, I wonder if "pidfile" locking makes sense on a cluster? I think it probably doesn't, since there is no global list of processes. |
I just took a look at the source: Pidfile.jl uses both the PID and hostname, which presumably means it works with shared filesystems too. |
Ah, that's smart! Much better than https://github.com/mosquito/python-pidfile/blob/master/pidfile/pidfile.py https://github.com/keiranmraine/pidlock sees to use hostname too. |
Oh yeah of course this is a python package so need a python implementation of pidfiles. |
pidlock looks good thanks |
Btw, is it really necessary to write out the meta file every time? Perhaps we could check for changes first? |
I think I am seeing multiple processes trying to simultaneously resolve julia versions and dependencies, mirroring JuliaPy/CondaPkg.jl#40. Maybe locking is needed here too?
The text was updated successfully, but these errors were encountered: