Skip to content

[claude] Stop an hg outage from restarting the lexbox pod - #2872

Open
myieye wants to merge 2 commits into
developfrom
claude/lexbox-liveness-without-hg
Open

myieye wants to merge 2 commits into
developfrom
claude/lexbox-liveness-without-hg

Conversation

@myieye

@myieye myieye commented Oct 30, 2026 •

Copy link
Copy Markdown
Collaborator

[Claude, autonomous]

Add /api/alive, which skips the hg-tagged check, and point lexbox's startup and liveness probes at it. When hgweb's CGI path broke in prod, the hg check failed /api/healthz, k8s restarted lexbox every 5 minutes and the whole site was down instead of just the hg-backed features. A liveness probe should only reflect faults a restart of that process can fix; hg's health isn't one.

/api/healthz is unchanged: the deploy workflow's version verification and the UI's version lookup read it, and the deploy check should keep requiring a reachable hg. The name matches the /api/alive that WebServiceDefaults already gives FwHeadless. The OTel trace filter now covers both paths. No test added: there's no WebApplicationFactory-style test home for endpoints in backend/Testing.

Verified: LexBoxApi.csproj builds; kubectl kustomize renders production, develop and staging with both lexbox probes on the new path; the GHA integration tests start the lexbox pod with it. Related: #2879 (version mismatch is Degraded, so HTTP 200).

🤖 Generated with Claude Code

https://claude.ai/code/session_01AM78WFuZRPxsWu4zM4eHNZ

Add /api/healthz/live, which skips the hg-tagged check, and point lexbox's
startup and liveness probes at it. /api/healthz keeps the hg check for the
deploy verification and the UI's version lookup. When hgweb's CGI path broke
in prod, the hg check failed /api/healthz, k8s restarted lexbox every 5
minutes and the whole site was down instead of just the hg-backed features.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AM78WFuZRPxsWu4zM4eHNZ
@coderabbitai

coderabbitai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 7 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 1a2d62a1-0f58-489d-a5b0-92f345b6e453
Commits

Reviewing files that changed from the base of the PR and between 5efc48f and fadb935.

Files selected for processing: 5
  • backend/LexBoxApi/AGENTS.md
  • backend/LexBoxApi/Otel/OtelKernel.cs
  • backend/LexBoxApi/Program.cs
  • backend/README.md
  • deployment/base/lexbox-deployment.yaml
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions github-actions Bot added the 📦 Lexbox issues related to any server side code, fw-headless included label Oct 30, 2026
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AM78WFuZRPxsWu4zM4eHNZ

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📦 Lexbox issues related to any server side code, fw-headless included

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants