Skip to content

Conversation

@uranusjr
Copy link
Member

Close #19618.

Due to a UI addition, the logical date of a manually-triggered DAG run
now has its sub-second part set to zero, instead of directly matching
the trigger time. This should be inconsequential in normal
circumstances, but apparently some people are relying on this sub-second
accuracy... for purposes I can't understand. But this is technically a
backward incompatible change.
@potiuk
Copy link
Member

potiuk commented Jun 13, 2022

ok. First time see: getCacheEntry failed: Cache service responded with 503 in Github Actions :)

@github-actions github-actions bot added the okay to merge It's ok to merge this PR as it does not require more tests label Jun 13, 2022
@github-actions
Copy link

The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

@uranusjr uranusjr merged commit ce48567 into apache:main Jun 13, 2022
@uranusjr uranusjr deleted the note-on-trigger-execution-date-change branch June 13, 2022 14:42
@eladkal
Copy link
Contributor

eladkal commented Jun 13, 2022

Thanks @uranusjr !

@ephraimbuddy ephraimbuddy added the type:doc-only Changelog: Doc Only label Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

okay to merge It's ok to merge this PR as it does not require more tests type:doc-only Changelog: Doc Only

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Execution_date not rendering after airflow upgrade

4 participants