-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
frequently getting error installing moto via pipenv (retry works) #2465
Comments
Unless pip provides some more information here or I can find a way to reproduce this (I haven't been able to), I'm not sure where to go from here. Does pinning moto to a specific version help? |
Note we are inside pipenv (venv) inside a docker; (python3-slim) - might be relevant; I can try pinning the version, and doing more testing for reproducibility if that helps. Feel free to fire ideas. |
I tried various reproduction attempts with a slimmed down setup in docker, so far no luck, mostly it works with this:
|
Bit the bullet and tried to recreate our docker + pipenv ven setup manually step-by-step;
This is the pipfile
Then do:
Then finally
Sigh. 🙌 I don't know why this is difficult to reproduce. :) I suspected build failure/conflict or something ... but pretty sure this has disproved it. I tried a few variants of this as well.... not able to reproduce outside of the automation/venv setup... |
Simply able to reproduce using our baked Docker image & entrance scripts that auto-install pipenv dev packages ... maybe it has something to do with the speed at which commands are executed in the automation/scripts environment ...(either affecting build, network, pkg conflicts, ...?) Ran our docker run script in a loop and its literally every time
Perhaps a good hint is that |
Was also wondering if pipenv install does something DIFFERENT when installing from
(REPRODUCED)Given this new result, we might have a "parallelization" type problem on our hands? Maybe pipenv is trying to install packages in parallel and they're clobbering one another? The KEY was volume-mounting our project's
|
I believe we can close as duplicate against pypa/pipenv#1356 |
(I'm not sure though why |
Ah, interesting. I learned something. It might be something related to either the number of dependencies Moto has or that they are common? Thanks for digging. |
Consider the following (simplified) Pipfile
Very frequently (nearly 50% of the time or more), our systems (regardless of source network locally, in aws cloud, etc) - often fails to install moto, and needs to retry.
This ONLY happens with the
moto
package and not others. Suspect maybe part of the build is failing first-time?Please advise.
The text was updated successfully, but these errors were encountered: