-
Notifications
You must be signed in to change notification settings - Fork 17
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
coiled-runtime still getting old coiled version sometimes #76
Comments
Richard says:
|
Thanks for surfacing @dchudz. @rrpelgrim could you post the output of your |
I can't reproduce this. I just create a new environment doing Packages installed
|
@jrbourbeau - yes, thankfully still had the notebook running. Here's the output:
And this was the output of
|
Not sure if this matters but I notice that @rrpelgrim is using |
So I'm noticing something weird here because technically
and in the list of installed packages the versions show ok, but then in the installed versions, that Richard shares we have.
@rrpelgrim is this an existing environment, is it possible that other packages you have in there, have requirements that is causing this issue? |
I'm on arm64 and I can't replicate the issue. |
@ncclementi - fyi the output of |
@rrpelgrim Oh I see, my bad for missing that. In that case, I'm afraid I'm not expecting to necessarily work, because there might be other packages in that environment that are blocking bringing the latest coiled version. We can't control other packages' dependencies and pins, I'm not sure this is a coiled-runtime issue. What I'd expect and at the moment I say we can guarantee is that when you install the coiled-runtime on a new fresh environment you should have the exact version of all the pin packages and the latest coiled version. cc: @dchudz |
I'm confused about how this matches up with what Richard described in Slack:
That made it sound like installing coiled-runtime somehow downgraded his coiled version. But looking at what Richard had installed before coiled-runtime ( Anyone understand...? |
AFAICT @ncclementi is right here. I used |
@dchudz and @rrpelgrim is there anything else pending on this issue to discuss or can we close it? |
sounds OK to close |
I don't have a lot of detail, sorry.
https://coiledcomputing.slack.com/archives/C029TTTHJ5A/p1650552363881219
The text was updated successfully, but these errors were encountered: