Spot clean try_number references to use ti.try_number#42633
Closed
dheerajturaga wants to merge 1 commit intoapache:mainfrom
Closed
Spot clean try_number references to use ti.try_number#42633dheerajturaga wants to merge 1 commit intoapache:mainfrom
dheerajturaga wants to merge 1 commit intoapache:mainfrom
Conversation
2 tasks
Contributor
|
These two values should be the same. Do you have repro steps to demonstrate that they differ? Or perhaps a test? |
Member
Author
Let me see if I can catch this somehow. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
Contributor
|
Author noted in #42549 (comment) that this is a false alarm. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Some tasks in airflow 2.10.2 are being launched with try number 0. However, the webserver is looking for logs starting with try number 1. Upon further investigation, I suspect that
{try_number}and{ti.try_number}are diverging leading to this.This is an attempt to cleanup references to
{try_number}related: #42549, #39336