-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Fixed #13723 - race condition on asset observer for older migration #13748
Conversation
Signed-off-by: snipe <[email protected]>
Signed-off-by: snipe <[email protected]>
Signed-off-by: snipe <[email protected]>
This pull request has been linked to Shortcut Story #23830: 2023_01_21_225350_add_eol_date_on_assets_table - migration fails to add eol_explicit column on older migrations. |
PR Summary
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a reasonable way to solve the problem. I think there are ways to save without firing observers, which might be another way to go about it - but this certainly does do the trick.
Hm, good point. I could perhaps try |
Signed-off-by: snipe <[email protected]>
@uberbrady can you peep this updated version? |
Signed-off-by: snipe <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this, it seems a bit cleaner - but if we really want to belt-and-suspenders this, I think it makes sense to have both in there at the same time. Especially since it’s so hard to test, I think I like that idea of trying to throw everything at the wall and just seeing what sticks.
Signed-off-by: snipe <[email protected]>
This should fix #13723, where there was a race condition firing a migration from earlier in 2023 which modifies the asset, but the observer touches fields that have not yet been created.
I mostly hate this (especially because we're going back in time to fix migrations) but this seems like the most sane way to clear the upgrade path.