This repository has been archived by the owner on Aug 4, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes
Fixes WordPress/openverse#1489 by @AetherUnbound
Description
This PR upgrades Airflow to v2.3.3, which includes the fix necessary in order to get our Sensors functioning properly. This jump does include a migration, and some important changes regarding the frontend. Fortunately we don't have any specific code related to the frontend, so AFAICT they don't affect us!
I tried running the SMK & Cleveland provider DAGs, as well as both the audio & image data refresh DAGs. I confirmed that all 4 ran successfully and that the latter 2 set the sensors to
up_for_reschedule
rather thanup_for_retry
.Testing Instructions
Note: You will need to run
just build
before any testing!Please double check that you can also run the data refresh DAGs locally, and that the sensor steps go to
up_for_reschedule
. See above for a picture of what that looks like.Checklist
Update index.md
).main
) or a parent feature branch.Developer Certificate of Origin
Developer Certificate of Origin