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

updating poetry lock and toml #294

Merged
merged 3 commits into from
Mar 31, 2023
Merged

updating poetry lock and toml #294

merged 3 commits into from
Mar 31, 2023

Conversation

scarrazza
Copy link
Member

@scarrazza scarrazza commented Mar 30, 2023

Updating to latest qibo 0.1.12.

Checklist:

  • Reviewers confirm new code works as expected.
  • Tests are passing.
  • Coverage does not decrease.
  • Documentation is updated.

pyproject.toml Outdated
python = ">=3.8, <4"
qibolab = "^0.0.1"
python = ">=3.8,<3.12"
qibolab = "^0.0"
Copy link
Member

Choose a reason for hiding this comment

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

Just for personal understanding: you suppressed the .1 because it would have been incompatible with .2, isn't it?

Copy link
Member Author

@scarrazza scarrazza Mar 30, 2023

Choose a reason for hiding this comment

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

Yeah, for this I don't have a strong opinion, we could simply set ^0.0.2 and then update version by version.
However, qibocal seems not compatible with qibo 0.1.12 (the <4 was locking the upgrade in the workflow). @andrea-pasquale are you aware of this problem (see failing tests below)?

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, for this I don't have a strong opinion, we could simply set ^0.0.2 and then update version by version.

As soon as possible, we should simply start using versions >0.1.0, and the problem will be partially solved.
With 0.x.y you only have the MAJOR+MINOR equivalent, and you lose the PATCH number. But with 0.0.x there is only MAJOR, and it is quite inconvenient...

Copy link
Contributor

Choose a reason for hiding this comment

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

However, qibocal seems not compatible with qibo 0.1.12 (the <4 was locking the upgrade in the workflow). @andrea-pasquale are you aware of this problem (see failing tests below)?

I think that the problem is related to the function copy_circuit that @wilkensJ introduced in the rb module.
@Edoardo-Pedicillo already fixed this issue in #288 which was merged in #266. As soon as we merge #266 to main and we merge main here tests should pass.

Copy link
Member

Choose a reason for hiding this comment

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

I believe you meant #261, not #266

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, sorry #261

@codecov
Copy link

codecov bot commented Mar 31, 2023

Codecov Report

Merging #294 (4662f51) into main (6a0e17d) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #294   +/-   ##
=======================================
  Coverage   37.84%   37.84%           
=======================================
  Files          42       42           
  Lines        2801     2801           
=======================================
  Hits         1060     1060           
  Misses       1741     1741           
Flag Coverage Δ
unittests 37.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@andrea-pasquale andrea-pasquale added this pull request to the merge queue Mar 31, 2023
Merged via the queue into main with commit 1e05a24 Mar 31, 2023
@andrea-pasquale andrea-pasquale deleted the uppoetry branch March 31, 2023 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants