Repository navigation
Make the bundle name less prominent in the Dag import error modals - #75958
Merged
bbovenzi merged 2 commits intoOct 29, 2026
Merged
Conversation
pierrejeambrun
added a commit
to astronomer/airflow
that referenced
this pull request
Oct 29, 2026
pierrejeambrun
added a commit
to astronomer/airflow
that referenced
this pull request
Oct 29, 2026
pierrejeambrun
marked this pull request as ready for review
October 29, 2026 12:56
pierrejeambrun
requested review from
bbovenzi,
choo121600,
guan404ming,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
October 29, 2026 12:57
choo121600
approved these changes
Oct 29, 2026
The bundle name was the first, bold item of each import error, so it drew more attention than the file that failed to parse. With a single bundle it carries no information at all.
pierrejeambrun
force-pushed
the
subtle-bundle-name-import-errors
branch
from
October 29, 2026 16:13
d6cbac0 to
804bfa4
Compare
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Oct 29, 2026
…or modals (apache#75958) * Make the bundle name less prominent in the Dag import error modals The bundle name was the first, bold item of each import error, so it drew more attention than the file that failed to parse. With a single bundle it carries no information at all. * Label the bundle as Bundle in the Dag import error modals (cherry picked from commit 38b3c45) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Oct 29, 2026
…or modals (apache#75958) * Make the bundle name less prominent in the Dag import error modals The bundle name was the first, bold item of each import error, so it drew more attention than the file that failed to parse. With a single bundle it carries no information at all. * Label the bundle as Bundle in the Dag import error modals (cherry picked from commit 38b3c45) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
ashb
pushed a commit
that referenced
this pull request
Oct 29, 2026
…or modals (#75958) * Make the bundle name less prominent in the Dag import error modals The bundle name was the first, bold item of each import error, so it drew more attention than the file that failed to parse. With a single bundle it carries no information at all. * Label the bundle as Bundle in the Dag import error modals (cherry picked from commit 38b3c45) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 30, 2026
…or modals (#75958) * Make the bundle name less prominent in the Dag import error modals The bundle name was the first, bold item of each import error, so it drew more attention than the file that failed to parse. With a single bundle it carries no information at all. * Label the bundle as Bundle in the Dag import error modals (cherry picked from commit 38b3c45) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
pierrejeambrun
added a commit
that referenced
this pull request
Oct 30, 2026
…or modals (#75958) (#75987) * Make the bundle name less prominent in the Dag import error modals The bundle name was the first, bold item of each import error, so it drew more attention than the file that failed to parse. With a single bundle it carries no information at all. * Label the bundle as Bundle in the Dag import error modals (cherry picked from commit 38b3c45) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 30, 2026
…or modals (#75958) (#75987) * Make the bundle name less prominent in the Dag import error modals The bundle name was the first, bold item of each import error, so it drew more attention than the file that failed to parse. With a single bundle it carries no information at all. * Label the bundle as Bundle in the Dag import error modals (cherry picked from commit 38b3c45) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
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.
The bundle name was the first, bold item of each import error, both in the dashboard's import errors list and in the single import error dialog of a bundle's files. It drew more attention than the file that actually failed to parse. When only one bundle exists, it tells nothing apart.
The bundle name is now shown after the file name, muted and right-aligned. It is hidden when the user can see a single bundle. The bundle count comes from a
limit=1request to the bundles endpoint, which only readstotal_entries.Several bundles
Single bundle
Before, this looked the same as with several bundles.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5.5) following the guidelines