Repository navigation
docs: Claude Code v2.1.310 - capacity alerts for self-hosted runners, VS Code untrusted-CA warning - #1408
Merged
Conversation
… VS Code untrusted-CA warning Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Night shift report
WHY THIS MATTERS: Anyone running self-hosted environments now gets ready-made Prometheus alerts for the failure that hurts most: sessions stuck because no runner is available. Before this, the sample rules covered poll errors and orchestrator disconnects but not lost capacity. Separately, VS Code users behind TLS-inspecting corporate proxies get a new log warning (v2.1.309+) that points straight at the
NODE_EXTRA_CA_CERTSfix. No version bump tonight; the manifest is still 2.1.310.HIGHLIGHTS:
self-hosted-environments-reference.md): a new "Alert on lost runners and waiting sessions" section with two sets of rules:ClaudeRunnersBelowFloorfires when the registered runner count stays under a floor for 10 minutes. The docs say to set the floor to about half the replica count, and warn that a missingnamespacelabel makes it read 0 and fire.ClaudeOrchestratorSessionsWaitingfires when pending sessions stay above 0 for 10 minutes.ClaudeOrchestratorQueueWaitHighfires when the p99 queue wait goes over 160s.SessionsWaitinggoes quiet about 2 minutes after the last orchestrator disconnects, so keepClaudeOrchestratorDisconnectedloaded.vs-code.md): from v2.1.309 the logs show a warning naming "an authority that Claude Code does not trust" on certificate errors. There's also a new note for Remote windows (WSL, SSH, dev containers): put the CA file andsettings.jsonedit on the remote system, not your local machine.mcp.md): a WebSocket server whose first connection fails can now be retried with Reconnect in the server's/mcpmenu (interactive terminal). The/mcp reconnect allwording was tidied up; it still needs v2.1.284+.desktop.md): small wording fix.API_TIMEOUT_MSjoinsPATHandCLAUDE_CONFIG_DIRas a variable with its own setup instructions, and the "exported variable missing" pointer no longer assumes~/.zshrcor~/.bashrc.Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning