-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update pixi lockfile #239
Update pixi lockfile #239
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #239 +/- ##
=======================================
Coverage 93.36% 93.36%
=======================================
Files 18 18
Lines 1988 1988
=======================================
Hits 1856 1856
Misses 132 132 ☔ View full report in Codecov by Sentry. |
@kklein I'm not sure about the following update
As far as I remember, the snowflake connector had issues with sqlalchemy 2.0. Or am I wrong? Or maybe now it got fixed? |
@ivergara Good catch! This used to cause problems. A somewhat recent release of This is also reflected in its dependencies: Since our snowflake tests also run through, I would think that upgrading the What are your thoughts? |
I'm fine going to SA2 then. No one should be using 1.4. unless compatibility issues like the one we were facing. Now the question is whether we want to have individual tests for snowflake with sa1 and sa2 or we keep only sa2. In any case, the wording of the label of the current snowflake test should be amended. I'm of the opinion we get rid of SA1. |
Explicit dependencies
db2-sa1 on {linux-64, win-64}
Implicit dependencies
{db2-py310, db2-py38, db2-py39, db2-sa1, lint} on {linux-64, osx-arm64}
{bigquery-py38, bigquery-sa1} on all platforms
{db2-py39, mssql-py39, postgres-py39, py39} on {linux-64, win-64}
db2-sa1 on {linux-64, win-64}
db2-sa1 on osx-arm64
Footnotes
Bold means explicit dependency. ↩ ↩2