Skip to content
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

Merged
merged 1 commit into from
May 29, 2024
Merged

Conversation

fd0r
Copy link
Collaborator

@fd0r fd0r commented May 17, 2024

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).

@fd0r fd0r requested a review from a team as a code owner May 17, 2024 09:16
@cla-bot cla-bot bot added the cla-signed label May 17, 2024
@fd0r fd0r force-pushed the update_cp_2_7_0rc1 branch 3 times, most recently from 9fba529 to ddf9dd3 Compare May 21, 2024 12:47
@fd0r fd0r force-pushed the update_cp_2_7_0rc1 branch 6 times, most recently from 71f336b to 26bca9f Compare May 23, 2024 08:52
@fd0r fd0r requested review from RomanBredehoft and a team May 23, 2024 11:12
jfrery
jfrery previously approved these changes May 23, 2024
Copy link
Collaborator

@jfrery jfrery left a 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!

Copy link
Collaborator

@RomanBredehoft RomanBredehoft left a 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 ?

@fd0r
Copy link
Collaborator Author

fd0r commented May 23, 2024

do we want to do this upgrade knowing this issue : zama-ai/concrete-internal#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?

@fd0r
Copy link
Collaborator Author

fd0r commented May 24, 2024

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.

@andrei-stoian-zama
Copy link
Collaborator

The nightly with the disable flag should be available

Copy link

⚠️ Known flaky tests have been rerun ⚠️

One or several tests initially failed but were identified as known flaky. tests. Therefore, they have been rerun and passed. See below for more details.

Failed tests details

Known flaky tests that initially failed:

  • tests/torch/test_compile_torch.py::test_compile_torch_or_onnx_networks[compile--FHE_simulation-model1-5-relu]- tests/torch/test_compile_torch.py::test_compile_torch_or_onnx_conv_networks[False-True-CNN_grouped-relu]

@fd0r
Copy link
Collaborator Author

fd0r commented May 27, 2024

Latest nightly still outputting warnings, let's wait for the next one!

@fd0r fd0r force-pushed the update_cp_2_7_0rc1 branch 5 times, most recently from ffe3d70 to e615e3b Compare May 29, 2024 08:32
@@ -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"
Copy link
Collaborator

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

Copy link
Collaborator Author

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

Copy link
Collaborator

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"
Copy link
Collaborator Author

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

Copy link
Collaborator

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 ?

Copy link
Collaborator Author

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

Copy link
Collaborator

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"
Copy link
Collaborator Author

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

Copy link
Collaborator

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 ?

Copy link
Collaborator Author

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.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm interesting, gotcha

@fd0r fd0r changed the title chore: update cp version to 2.6.2 chore: update cp version to 2.6.2dev20250529 May 29, 2024
Copy link

Coverage passed ✅

Coverage details

---------- coverage: platform linux, python 3.8.18-final-0 -----------
Name    Stmts   Miss  Cover   Missing
-------------------------------------
TOTAL    7595      0   100%

59 files skipped due to complete coverage.

@fd0r fd0r requested a review from RomanBredehoft May 29, 2024 11:29
Copy link
Collaborator

@RomanBredehoft RomanBredehoft left a 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

@fd0r fd0r merged commit 9a8121c into main May 29, 2024
12 checks passed
@fd0r fd0r deleted the update_cp_2_7_0rc1 branch May 29, 2024 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants