dstandish commented on issue #48844: URL: https://github.com/apache/airflow/issues/48844#issuecomment-2787151159
so, here's what we need to do... **first thing is, we need to revert the changes to the serdag structure so that the scheduler and webserver will not run into these issues** and before make any changes to serdag structure, we'll need to implement a versioning scheme so this can be handled properly in the future additionally, this issue has revealed some additional questions why is it that reserializing fixes this for a dag in flight? jed says that the scheduler should continue to use the old serdag (so it should still be broken after reserializing). reserialization is supposed to only add new versions; -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
