Conversation
1 task
Member
Author
|
Follow up issue: |
Member
Author
|
cc: @uranusjr just in case you have time to double check that this fixes it on your side. |
jscheffl
approved these changes
Jul 28, 2025
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker e83ca8e v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
Member
Author
RoyLee1224
pushed a commit
to RoyLee1224/airflow
that referenced
this pull request
Jul 31, 2025
ferruzzi
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Aug 7, 2025
fweilun
pushed a commit
to fweilun/airflow
that referenced
this pull request
Aug 11, 2025
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
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.

closes: #52272
This just fixes the bars. Indeed as mentioned in the related issue we might want to reconsider how we build this because the total number of slots displayed can grow beyond the total pool slots. This is caused by the fact that we display in the same way state that take up a pool slots and those that do not. (QUEUE, RUNNING, OPEN) should always be included, (DEFERRED) should only be included if configured, and SCHEDULED / DEFERRED (if not configured) should probably be displayed outside of that pool occupancy bar, to not confuse users.
This is a bigger effort to improve the UI to not have this confusion anymore and find a way to clearly display the difference between all kind of slots. (also because this component is shared with multiple pools summary) for the short term I just fixed the bar, and will create an issue for the follow up.
Before
After: