potiuk commented on pull request #21464: URL: https://github.com/apache/airflow/pull/21464#issuecomment-1034041354
> Do we know how to reliably trigger the bug so we can test it's fixed when we reintroduce this changeset? Actually .... this does not seem like it ... The last run when I was using `Public Runners` actually triggered it - so my hypothesis was wrong. https://github.com/apache/airflow/runs/5128289741?check_suite_focus=true#step:7:2081 ```` airflow-webserver_1 | File "/home/airflow/.local/lib/python3.7/site-packages/sqlalchemy/orm/dependency.py", line 553, in process_deletes airflow-webserver_1 | state, child, None, True, uowcommit, False airflow-webserver_1 | File "/home/airflow/.local/lib/python3.7/site-packages/sqlalchemy/orm/dependency.py", line 610, in _synchronize airflow-webserver_1 | sync.clear(dest, self.mapper, self.prop.synchronize_pairs) airflow-webserver_1 | File "/home/airflow/.local/lib/python3.7/site-packages/sqlalchemy/orm/sync.py", line 88, in clear airflow-webserver_1 | "column '%s' on instance '%s'" % (r, orm_util.state_str(dest)) airflow-webserver_1 | AssertionError: Dependency rule tried to blank-out primary key column 'ab_permission.id' on instance '<Action at 0x7ff72cb09310>' ``` We need to look more. But it seems that it's rather reliably triggered on Public runners. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
