-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Feedback on the new resolution mechanism #230
Comments
Also on
https://github.com/jupyter/notebook/actions/runs/8539292958/job/23396548527?pr=7312 |
I guess there is nothing to do here. With bumping a few pins the job is now passing for me. I just think that maybe this should have been a new release given how many downstreams are affected? But maybe it is ok if it does find at least one true positive where lack of a pin made a difference (so far I have not seen it though). |
Yes, and it's also a bit tedious to fix. For example in the case of the notebook issue reported above, the default
While doing a plain In this case, it looks like it's not even fixable in notebook, but requires a fix in |
OK the So it looks like that would mean fixing the dependencies in |
Yes, the thing worries me is that even if we do some magic with the pins the final resolution may not represent the actual resolution users get when installing using |
I think the errors we're seeing in practice will be fixed by using |
I disagree, this is an "advanced" check, and we're making it a bit stricter and more correct. |
Ah, I do see the point about affecting regular installs. If the next release doesn't fix that in most cases, we can make it opt-in for regular installs. |
Okay, no, now |
Thank you! |
Also many other jobs (e.g. https://github.com/krassowski/jupyter_server/actions/runs/8542681567/job/23404855225) seem to be failing with:
but this might be unrelated
Results in:
The text was updated successfully, but these errors were encountered: