fix(health-monitor): add reconnect grace for gateway reconnects#73989
fix(health-monitor): add reconnect grace for gateway reconnects#73989openclaw-clownfish[bot] wants to merge 2 commits into
Conversation
|
Closing this PR because the author has more than 10 active PRs in this repo. Please reduce the active PR queue and reopen or resubmit once it is back under the limit. You can close your own PRs to get back under the limit. |
Greptile SummaryThis PR adds a shared reconnect grace window to the channel health monitor and readiness checker so that running-but-recently-disconnected channels (e.g., mid-provider reconnect loop) are not restarted prematurely. It extracts Confidence Score: 5/5Safe to merge; the implementation is correct, well-bounded, and covered by focused regression tests. No logic bugs found. The lifecycle guard ( No files require special attention. Reviews (2): Last reviewed commit: "fix(health-monitor): add reconnect grace..." | Re-trigger Greptile |
|
Thanks for the context here. I swept through the related work, and this is now duplicate or superseded. Keep open: current main still marks a running managed channel with Canonical path: Close this stale PR. The latest review rated it F, the branch still lacks merge-ready proof, and there has been no human follow-up after the durable review. So I’m closing this here because the remaining work is already tracked in the canonical issue. Review detailsBest possible solution: Close this stale PR. The latest review rated it F, the branch still lacks merge-ready proof, and there has been no human follow-up after the durable review. Do we have a high-confidence way to reproduce the issue? Yes from source inspection: current main marks Is this the best way to solve the issue? No, not as submitted: reconnect grace is a plausible fix, but this branch is not the best merge shape until it is refreshed, all current callers are updated, and the default restart-delay tradeoff is owner-approved. Security review: Security review cleared: The diff touches gateway TypeScript, tests, and changelog text only; I found no dependency, workflow, credential, install, publish, or supply-chain change. AGENTS.md: found and applied where relevant. What I checked:
Likely related people:
Codex review notes: model internal, reasoning high; reviewed against eb417fa206e6. |
|
/clownfish automerge |
|
Clownfish is on the reef for this PR. 🐠 I tagged A maintainer can call |
|
🦞🦞 Source: I added |
|
🦞🦞 Repair: rebased this branch deterministically; Codex fix/edit was not needed. Current state: exact-head review queued immediately; GitHub checks and the review verdict gate final merge. Automerge progress:
|
d9659eb to
8007e25
Compare
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
8007e25 to
60a6452
Compare
|
🦞✅ Source: Why human review is needed: What the maintainer can do as a next step: I added |
|
This pull request has been automatically marked as stale due to inactivity. |
|
This pull request has been automatically marked as stale due to inactivity. |
|
🦞✅ Reason: structured ClawSweeper close marker: close-required (sha=60a6452d4b8ba35891f1728053d13c8ab6eaa6c1) Closed:
|
Repairs the existing #45712 branch rather than replacing it.
Summary:
Validation:
Credit: based on #45712 by @cass-clearly / Cass.
ProjectClownfish replacement details:
! [remote rejected] HEAD -> fix/health-monitor-reconnect-grace (refusing to allow a GitHub App to create or update workflow
.github/workflows/auto-response.ymlwithoutworkflowspermission)error: failed to push some refs to 'https://github.com/cass-clearly/openclaw.git'