Repository navigation
Fix DecreasingPriorityStrategy example by initializing try_number before weight evaluation - #62148
Conversation
3e0254c to
04d4bd8
Compare
455f2f4 to
89df73b
Compare
89df73b to
748e769
Compare
748e769 to
9455275
Compare
|
Converted to Draft as we try to make an order in our PRs. |
|
@aeroyorch This draft PR has not had author activity for 54 days. Before anyone can review it, it needs to meet our Pull Request quality criteria. Here is a summary of what still needs work; once those items are addressed, mark the PR ready for review. Issues found:
What to do next:
There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack. |
be80734 to
7163c3d
Compare
7163c3d to
3651315
Compare
03c3bd5 to
514373f
Compare
514373f to
4127311
Compare
c95601d to
63aa906
Compare
|
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. |
63aa906 to
fa9313f
Compare
fa9313f to
a1b219d
Compare
0981f2f to
ea0ecf2
Compare
ea0ecf2 to
0a009d1
Compare
0a009d1 to
ddb26f7
Compare
DecreasingPriorityStrategy example by initializing try_number before weight evaluation
|
I think the PR is failing due to the PR title.. |
…ore weight evaluation
ddb26f7 to
da7b64d
Compare
Description
The documented
DecreasingPriorityStrategycan fail becauseget_weight()may run whileTaskInstanceis still partially initialized, soti.try_numberis not ready. This PR applies a small fix by initializingtry_numberbeforerefresh_from_task()and adds a regression test case forDecreasingPriorityStrategy.Was generative AI tooling used to co-author this PR?