-
Notifications
You must be signed in to change notification settings - Fork 121
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
chore: update cp version to 2.6.2dev20250529 #684
Conversation
9fba529
to
ddf9dd3
Compare
71f336b
to
26bca9f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to do this upgrade knowing this issue : https://github.com/zama-ai/concrete-internal/issues/717 ?
Very good question @RomanBredehoft since this isn't a release version it's fine with me with the verbose stuff but maybe @andrei-stoian-zama can have the last word on that? |
Writing here what was decided on slack. We wait to have a flag to disable these warnings and let the Concrete team investigate where these overflows come from and how badly they impact us. |
The nightly with the disable flag should be available |
|
Latest nightly still outputting warnings, let's wait for the next one! |
ffe3d70
to
e615e3b
Compare
@@ -19,7 +19,7 @@ OPEN_PR="true" | |||
# Force the installation of a Concrete Python version, which is very useful with nightly versions | |||
# /!\ WARNING /!\: This version should NEVER be a wildcard as it might create some | |||
# issues when trying to run it in the future. | |||
CONCRETE_PYTHON_VERSION="concrete-python==2024.4.19" | |||
CONCRETE_PYTHON_VERSION="concrete-python==2.6.2.dev20240529" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw, now that nightlies are completely public and handled directly in the lock file, I think we can safely remove this and all related parts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's correct, let's do that in a follow up PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now we target Zama's index. Once the newest version is on pypi we'll need to change it. (it will just be about removing the source argument from pyproject.toml).
@@ -34,7 +34,8 @@ readme = "README.md" | |||
# Investigate if it is better to fix specific versions or use lower and upper bounds | |||
# FIXME: https://github.com/zama-ai/concrete-ml-internal/issues/2665 | |||
python = ">=3.8.1,<3.11" | |||
concrete-python = "2.6.0-rc1" | |||
concrete-python = {version="==2.6.2.dev20240529", source = "zama-pypi"} | |||
# concrete-python = ">=2.6.2.dev20240523,<3.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't use that requirement because 2.6.2 > 2.6.2dev, so poetry lock would install 2.6.2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but we want to fix CP's version no ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well that's a good question. I'm not so sure about that.
In theory we should only require the major version of a package unless we know that there is a change that breaks our code base.
Introducing more flexibility here would let us avoid the need of doing a patch release whenever Concrete Python does ones. That wouldn't be reflected in the lock file though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah for our other libraries I pretty much agree, but CP is a bit different, especially since we consider nightly versions and I don't think we would want poetry to consider the most recent nightly each time we update the lock (?)
@@ -78,6 +85,8 @@ mdformat = "^0.7.14" | |||
mdformat_myst = "^0.1.4" | |||
mdformat-toc = "^0.3.0" | |||
pip-audit = "^2.1.0" | |||
types-requests = "^2.32.0" | |||
requests="^2.32.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
requests
was installed by type-requests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but didn't you removed types-requests
initially ? why is it needed then ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need requests for dev scripts. @jfrery had removed it some time ago but by keeping type-requests
we were in fact still installing it. It was weird to me that we had the type stubs of a packages that we weren't requiring. So I tried removing it but everything broke. So I added back requests here since I feel like it's more explicit than relying on the fact that type-requests
requires requests
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm interesting, gotcha
Coverage passed ✅Coverage details
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks ! just have a few questions, which could be handled in a following PR if needed
For now we target Zama's index but once 2.6.2 is on pypi we'll need to change it (it will just be about removing the source argument from pyproject.toml).