potiuk opened a new pull request, #77132:
URL: https://github.com/apache/airflow/pull/77132

   The fork CI monitor's Slack notes about failed calls named only the 
exception type, for example "reporting `CI run started` for project CI failed: 
GitHubError". That failure came up three times during the pilot (2026-11-06 
twice, 2026-11-11) and could not be diagnosed from Slack.
   
   With this change, such notes and items name the exception and the first line 
of its message, for example "… failed: GitHubError: HTTP 502: Bad Gateway". The 
text is capped at 200 characters, and the run log still has the full error.
   - A failed `gh` call's message starts with the call's arguments, which for 
GraphQL include the whole query. Those are left out for all four forms the 
client produces: `failed:`, `still failing after N attempts:`, `still rate 
limited after N attempts`, and `timed out after Ns`.
   - A failure that persists gives the same text on every run, so it is still 
posted once.
   
   This applies to five places:
   - reporting `CI run started` for project CI;
   - listing the pull requests with `use project ci`;
   - reporting `CI passed` for `use project ci`;
   - the two per-pull-request "`CI passed` not updated" items.
   
   The design doc's "Unknown failures and attention items go to Slack" section 
describes it.
   
   Tested: all breeze tests pass, including new ones for the message formats; 
static checks pass.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Claude Opus 5)
   
   Generated-by: Claude Code (Claude Opus 5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01NyQq9U7i5HhjDgrQ9qd3gq
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to