You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fc27c38
Browse filesBrowse the repository at this point in the historyBrowse files
feat(triage-contracts): make Triage's waits overridable and publish them in the release
Every wait the hub, listener and manager share is one named timing in
triage-contracts with its production value as default and a TRIAGE_*_MS
override. The hub reads them once as it starts and writes the listener's
and manager's share into their release.json, since a workflow's process
gets none of the hub's environment; a tree without them runs on the
defaults. The hub's deploy hold stays derived from the same ready window
the listener waits.
* A pull request's webhook events go out as one mail once none arrived for the quiet period, or at most four quiet periods after the first; the window must close before the reconciler gives up on its queued head.
303
285
* A new commit or a newly opened pull request waits only for the burst, long enough to take in the review requests, labels and assignees GitHub delivers with it within a second or so.
thrownewError(`TRIAGE_COALESCE_QUIET_MS must be below ${policy.unstartedAfterMs/4}: four times it must stay under the ${policy.unstartedAfterMs} ms a queued head may wait to start`);
Copy file name to clipboardExpand all lines: docs/SELF_HOST.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -291,6 +291,11 @@ All optional; the defaults suit most installs.
291
291
| Variable | Default | Effect |
292
292
| --- | --- | --- |
293
293
|`TRIAGE_RECONCILE_INTERVAL_MS`| 300000 | How often the hub re-queues open pull requests whose latest commit has no verdict. |
294
+
|`TRIAGE_RECONCILE_RETRY_MS`| 15000 | How soon a pass that could not reach a host's listener tries again, doubling up to two minutes. |
295
+
|`TRIAGE_MANAGER_READY_MS`| 120000 | How long Triage waits for a pull request's just-started manager to come up before it starts another in its place. |
296
+
|`TRIAGE_MANAGER_START_GRACE_MS`| 120000 | How long a just-started manager may take to come up and still keep its pull request. |
297
+
|`TRIAGE_MANAGER_POLL_MS`| 30000 | How often a pull request's manager checks again while it waits for CI, the decision model or code review. |
298
+
|`TRIAGE_WAKE_POLL_MS`| 2000 | How often Triage checks whether a just-started manager has come up. |
294
299
|`TRIAGE_MAX_IN_FLIGHT`| 5 | Pull request heads a workspace may have queued or running at once. |
295
300
|`TRIAGE_CAPPED_RETRY_MS`| 21600000 | How long a head that ran out of attempts waits before a fresh set. |
296
301
|`TRIAGE_STALLED_AFTER_MS`| 300000 | How long a pull request may wait for Triage to start before the hub raises the alarm for its host in that workspace: the `triage_stalled` log line, a notice in the portal, and, with [email](#email) set up, one email to the workspace's owners and admins; `triage_stall_cleared` and a second email follow once Triage starts a pull request on that host again. The alarm fires within this time plus one `TRIAGE_LIVENESS_INTERVAL_MS`. |
0 commit comments