Observations
We discovered two spots where using v2.2.1 goes south on nightly scheduled CI runs of two downstream projects after upstream driver package releases two days ago. They can be healed by downgrading to v2.1.x.
cratedb-fivetran-destination
Uses crate==2.2.1, sqlalchemy-cratedb==0.42.0.dev2, and sqlalchemy==2.0.51.
See failures at CI run #27739496576 and CI run overview.
FAILED tests/test_adapter.py::test_api_migrate_drop_column_in_history_mode_operation_timestamp_wrong
crate.client.exceptions.ProgrammingError:
ColumnUnknownException[Column data unknown]
cratedb-toolkit
Uses crate==2.2.1, sqlalchemy-cratedb==0.43.0, and sqlalchemy==1.4.54.
See failures at CI run #27736731406 and CI run overview.
FAILED tests/adapter/test_pymongo.py::test_pymongo_insert_one_single
crate.client.exceptions.ProgrammingError:
SQLParseException[line 1:49: no viable alternative at input 'VALUES (%']
Evaluation
Apologies that we haven't been able to come up with a concise reproducer about this incident yet, derived from investigating the relevant downstream test cases that went south. The primary intention of this report is to acquire attention and resources on your end. The outcome might converge into yanking the release, relevant fixes to the driver packages, or advises how to use them correctly in enumerated downstream scenarios after potential changes.
Workaround
A downgrade to previous driver versions brought immediate success to heal impacted spots.
Yank v2.2.1?
I've just yanked crate-2.2.0 from PyPI, because it showed anomalies on the SQLAlchemy dialect, as demonstrated above.
@bgunebakan and @florinutz: I will not do that for crate-2.2.1; please discuss and decide. Please also share your PyPI usernames, so you can be added as project maintainers and receive capabilities to perform corresponding actions. Thanks!
References
Observations
We discovered two spots where using v2.2.1 goes south on nightly scheduled CI runs of two downstream projects after upstream driver package releases two days ago. They can be healed by downgrading to v2.1.x.
cratedb-fivetran-destination
Uses crate==2.2.1, sqlalchemy-cratedb==0.42.0.dev2, and sqlalchemy==2.0.51.
See failures at CI run #27739496576 and CI run overview.
cratedb-toolkit
Uses crate==2.2.1, sqlalchemy-cratedb==0.43.0, and sqlalchemy==1.4.54.
See failures at CI run #27736731406 and CI run overview.
Evaluation
Apologies that we haven't been able to come up with a concise reproducer about this incident yet, derived from investigating the relevant downstream test cases that went south. The primary intention of this report is to acquire attention and resources on your end. The outcome might converge into yanking the release, relevant fixes to the driver packages, or advises how to use them correctly in enumerated downstream scenarios after potential changes.
Workaround
A downgrade to previous driver versions brought immediate success to heal impacted spots.
crate<2.2cratedb-fivetran-destination#193crate<2.2andsqlalchemy-cratedb<0.43cratedb-toolkit#843Yank v2.2.1?
@bgunebakan and @florinutz: I will not do that for
crate-2.2.1; please discuss and decide. Please also share your PyPI usernames, so you can be added as project maintainers and receive capabilities to perform corresponding actions. Thanks!References