5678f219cd
The pattern of adding a column and then reading a table with it no longer works in SQLAlchemy 1.3.20. This has been reported upstream [1] and apparently we're doing the wrong thing by reusing a column object twice. We need to disable the non-standalone job since it's really broken now, and this fix is blocking bifrost. [1] https://github.com/sqlalchemy/sqlalchemy/issues/5669 Change-Id: I2fb07413e8f421f39b24acf1272771ee2097b195 |
||
---|---|---|
.. | ||
578f84f38d_inital_db_schema.py | ||
882b2d84cb1b_attribute_constraints_relaxing.py | ||
2970d2d44edc_add_manage_boot_to_nodes.py | ||
18440d0834af_introducing_the_aborting_state.py | ||
b55109d5063a_added_scope_column_to_rules_table.py | ||
bf8dec16023c_add_introspection_data_table.py | ||
d2e48801c8ef_introducing_node_state_attribute.py | ||
d00d6e3f38c4_change_created_finished_at_type.py | ||
d588418040d_add_rules.py | ||
e169a4a81d88_add_invert_field_to_rule_condition.py |