Skip to content

Improve auto-triage display labels and log extraction#63687

Merged
potiuk merged 2 commits intoapache:mainfrom
potiuk:improve-triage-display-labels
Mar 16, 2026
Merged

Improve auto-triage display labels and log extraction#63687
potiuk merged 2 commits intoapache:mainfrom
potiuk:improve-triage-display-labels

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Mar 16, 2026

Improve user-facing labels in auto-triage output and optimize log extraction.

  • Replace "flagged"/"candidate" with "issues found" in all user-facing tables and status messages
  • Show per-action result (drafted/commented/closed/skipped) in the summary timing table instead of generic "flagged"
  • Extract only the last ~1000 lines of CI log files to reduce memory usage
  • Focus error extraction on the last error cluster for more relevant failure output

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Opus 4.6

Generated-by: Claude Opus 4.6 following the guidelines

potiuk added 2 commits March 16, 2026 16:46
- Replace "flagged"/"candidate" with "issues found" in all user-facing
  tables and status messages for clearer triage output
- Show per-action result (drafted/commented/closed/skipped) in summary
  table instead of generic "flagged"
- Extract log tail (last ~1000 lines) to reduce memory usage on large
  CI log files
- Focus error extraction on last error cluster for more relevant output
- Fix return type of _get_cached_status to Any (payload can be dict or list)
- Annotate renderables list to accept both str and Text objects
@potiuk potiuk force-pushed the improve-triage-display-labels branch from 580db73 to 429ed26 Compare March 16, 2026 15:46
@potiuk potiuk merged commit 2323376 into apache:main Mar 16, 2026
134 checks passed
@potiuk potiuk deleted the improve-triage-display-labels branch March 16, 2026 21:01
@github-actions
Copy link

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 2323376 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants