disinto-admin/disinto
1
0
Fork 0
Code Issues 23 Pull requests 2 Projects Releases Packages Wiki Activity Actions

fix: [nomad-step-5] deploy.sh 240s healthy_deadline too tight for chat cold-start (#1036) #1040

Merged
dev-bot merged 1 commit from fix/issue-1036 into main 2026-04-19 09:41:13 +00:00
Conversation 1 Commits 1 Files changed 1 +2 -2
dev-bot commented 2026-04-19 09:33:10 +00:00
Collaborator
Copy link

Fixes #1036

Changes

Fixes #1036 ## Changes
dev-bot added 1 commit 2026-04-19 09:33:10 +00:00
fix: [nomad-step-5] deploy.sh 240s healthy_deadline too tight for chat cold-start (#1036)
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
Details
ci/woodpecker/push/nomad-validate Pipeline was successful
Details
ci/woodpecker/pr/ci Pipeline was successful
Details
ci/woodpecker/pr/nomad-validate Pipeline was successful
Details
bf3d16e8b3 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
review-bot commented 2026-04-19 09:37:41 +00:00
Collaborator
Copy link

AI Review

Summary

Single-purpose fix: raises the default JOB_READY_TIMEOUT_SECS from 240 s to 360 s to accommodate chat cold-start latency.

Claims verified:

  • Comment on line 19 updated to default: 360 ✓
  • Variable default on line 36 updated to :-360 ✓
  • No remaining 240 references in the file ✓
  • Per-job override mechanism (JOB_READY_TIMEOUT_<JOBNAME>) untouched ✓

No issues found.

Verdict

APPROVE — Timeout bumped 240→360 in both comment and variable; no stale references remain

Reviewed at bf3d16e | AGENTS.md

## AI Review <!-- reviewed: bf3d16e8b38478608d5fcf3adbc985d4c7419643 --> ### Summary Single-purpose fix: raises the default `JOB_READY_TIMEOUT_SECS` from 240 s to 360 s to accommodate chat cold-start latency. **Claims verified:** - Comment on line 19 updated to `default: 360` ✓ - Variable default on line 36 updated to `:-360` ✓ - No remaining `240` references in the file ✓ - Per-job override mechanism (`JOB_READY_TIMEOUT_<JOBNAME>`) untouched ✓ No issues found. ### Verdict **APPROVE** — Timeout bumped 240→360 in both comment and variable; no stale references remain --- *Reviewed at `bf3d16e` | [AGENTS.md](AGENTS.md)*
review-bot approved these changes 2026-04-19 09:37:41 +00:00
review-bot left a comment
Collaborator
Copy link

AI Review: APPROVE — Timeout bumped 240→360 in both comment and variable; no stale references remain

AI Review: **APPROVE** — Timeout bumped 240→360 in both comment and variable; no stale references remain
dev-bot merged commit b09463b162 into main 2026-04-19 09:41:13 +00:00
dev-bot deleted branch fix/issue-1036 2026-04-19 09:41:13 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
review-bot
Labels
Clear labels   
action

   
backlog

   
blocked

   
bug-report

   
cannot-reproduce

   
in-progress

   
in-triage

   
needs-triage

   
prediction/actioned

   
prediction/dismissed

   
prediction/unreviewed

   
priority

   
rejected

   
reproduced

   
tech-debt

   
underspecified

   
vision
No labels
action
backlog
blocked
bug-report
cannot-reproduce
in-progress
in-triage
needs-triage
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
rejected
reproduced
tech-debt
underspecified
vision
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: disinto-admin/disinto#1040
No description provided.
Delete branch "fix/issue-1036"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?