kevinveenbirkenbachandClaude Opus 5.5 86998924d9 fix(ci): name the gh failure when the retrigger finds no inputs ...

The retrigger guard aborted with 'its job log records no inputs' while _gh(check=False) dropped gh's stderr, so a transient log read failure and a moved Inputs block looked the same. _gh now takes an errors list instead of check: given, a failure appends gh's last stderr line with URL query strings cut (job logs redirect to signed blob URLs) and yields an empty string; absent, it aborts as before. inputs_from_jobs passes such a list through, and dispatched_priority appends how many log reads failed and the last error, or that none failed.

MEDUSA findings accepted as false positives (unchanged lines, no SQL or untrusted argv; independent skeptic review): MEDUSA-FTSCAN-231 runs.py:80 and runs.py:318, B603 gh.py:27 and gh.py:79, B105 runs.py:36.

🎯 Fix: 95 %
💥 Break: 2 %
💸 Cost: –
⏱️ Time: –
🛡️ Security: 100 %
🏆 Score: 93
🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 %

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-07 06:12:50 +00:00

..

deploy

fix(ci): name the gh failure when the retrigger finds no inputs

2026-11-07 06:12:50 +00:00

inventory

refactor(provision): group the services disabler modules in a services package

2026-11-04 12:23:07 +01:00

recover

fix(recover): restore an NFS generation onto the export base it was taken from

2026-10-28 17:56:26 +01:00

roles

fix(cli): create role markers and the placement lock owner-only

2026-11-05 17:02:47 +00:00

__init__.py

…