Skip to content

Bound runs by time and fix two report rendering errors - #22

Merged
alexandre-daubois merged 2 commits into
mainfrom
triage/run-time-limit
Oct 28, 2026
Merged

alexandre-daubois merged 2 commits into
mainfrom
triage/run-time-limit

Conversation

@alexandre-daubois

Copy link
Copy Markdown
Member

A run now starts an advisory only while 30 minutes remain of its 3 hours 50 minutes, which fits a 4-hour job, instead of stopping after 10 advisories. A failed duplicate search now says so instead of rendering "None found among the repository advisories.". A policy point ending with a period no longer renders as "point.: reason".

A run now starts an advisory only while 30 minutes remain of its 3 hours 50 minutes, which fits a 4-hour job, instead of stopping after 10 advisories.
A failed duplicate search now says so instead of rendering "None found among the repository advisories.".
A policy point ending with a period no longer renders as "point.: reason".
An agent run that fails without a valid report is run again after a minute, so a model provider briefly overloaded or dropping its stream no longer costs a triage attempt or publishes a report without its duplicate search.
@alexandre-daubois
alexandre-daubois merged commit e3f3912 into main Oct 28, 2026
7 checks passed
@alexandre-daubois
alexandre-daubois deleted the triage/run-time-limit branch October 28, 2026 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant