-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Creation of opam switch fails if the cwd get erased #4455
Comments
Indeed, it's not the most usual case :)
Do you have another workflow? |
"Workflow" is hyperbole :-) but it was 2. I can reproduce on macOS 10.15.7 with:
Now in another terminal
|
Ok! I don't have a macos available to test. If you have a moment, can you try to give the full log of the switch creation with a debug level to 3? It is quite long, maybe on a gist |
@rjbou I can give you access to my test mac mini i got off of ebay a couple of months ago. Just send me your public key in DM if you'd want that |
Sorry @rjbou I missed your message here you have: https://gist.github.com/dbuenzli/fb5435310654dee8ab0193e1d16122e3 |
Thanks @kit-ty-kate I'll keep this in mind for further mac-related experiments. On the issue itself: at each process launch, opam retrieve the cwd (to rollback to the good dir), so when the directory is removed, the |
I don't think it's a super important issue so don't hesitate to close if it makes it for easier operations.
But it seems that if you are in a directory, invoke
opam switch create
to create a non-local switch and then somehow erase that directory you end up with:The text was updated successfully, but these errors were encountered: