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

Atomic install #19

Open
mottosso opened this issue Jul 16, 2019 · 3 comments
Open

Atomic install #19

mottosso opened this issue Jul 16, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@mottosso
Copy link
Owner

Rez is currently able to resolve a package, prior to it having been completely installed. That's a bug.

@mottosso mottosso added the bug Something isn't working label Jul 16, 2019
@mottosso
Copy link
Owner Author

Turns out this happen during the final copy from temporary directory into the package repository. The install itself is fine, but the copy is a plain shutil.copytree which presumably copies in the order returned by os.listdir (alphabetical). The easy solution would be to just pop the package.py file, and append it to the list.

@mottosso
Copy link
Owner Author

The reason this was a problem in this case was because the final copy was really really slow, to a VPN running at ~10kb/sec. So the install went well, in under a second, but then the actual copy took about 10 minutes, during which time the package would appear broken.

@mottosso
Copy link
Owner Author

mottosso commented Jul 31, 2019

Use rez cp for this. Post-install of pip packages, convert it locally as well, and then finally rez cp the package onto the server. That way we'll piggyback on the safety and robustness built into the rez cp command.

Can currently be done manually.

rez env pipz -- install six
rez cp six --dest-path /server/packages

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant