-
Notifications
You must be signed in to change notification settings - Fork 337
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
'rez build --install --prefix' error #858
Comments
I haven't seen this error, have you determined that it's related to running within a container? The second stacktrace looks like it's simply caused by a missing import for the WindowsError, I will look into that. In the meantime perhaps if you could narrow down the repro, if possible. Cheers! |
Hit a simillar problem: https://github.com/nerdvegas/rez/blob/master/src/rez/serialise.py#L76 |
The first thing I'd investigate is whether a newer version of
`atomicwrites` is necessary.
A
…On Tue, Sep 22, 2020 at 9:56 AM alexxbb ***@***.***> wrote:
Hit a simillar problem: NameError: name 'WindowsError' is not defined
https://github.com/nerdvegas/rez/blob/master/src/rez/serialise.py#L76
<http://url>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#858 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMOUSVPYAXLA4MRSP5J4JDSG7R25ANCNFSM4K2MWD2Q>
.
|
Wonder why is this windows-specific WindowsError in the code in the first place? I'm getting errors on Linux with Python2. |
Oh, I haven't seen failures with atomiwrites on linux before, I'd assumed you were on Windows. Would it be possible to isolate this to a small repro using atomicwrites only? I am assuming this is an edge case we've not seen before - if this were failing in the general case, I'd have gotten loads of bug reports. |
rez-pip --install --release --python-version=2.7 python-gitlab
Without --release it installed locally just fine. Hope this helps. Thanks. |
I have encountered the same issue using debian. This seems to happen because some fs don't handle sync for directories (used to ensure atomicity) : untitaker/python-atomicwrites#17 my current workaround is to call rez pip on a local directory and use rsync before and after the call to transfert the newly installed package Since atomicity can't be guaranteed within Network repositories, it would be nice to use a simple (non atomic) method if atomicwrites fail with this error (OSError: [Errno 22]) |
fixed in #998 |
Hi there!
We encountered the following error while deploying a library of ours in a specific directory with rez on a python's docker image through Gitlab CI/CD.
We'd be grateful if you could tell us how to resolve this issue by ourselves or if you could fix it!
We might have missed some context or information in this comment; please tell us so if necessary.
Many thanks in advance.
The text was updated successfully, but these errors were encountered: