Fix multi-env prod ports: 70xxx exceeds 65535, use 60xxx#49
Merged
Conversation
The prod band shipped in v1.6.0 was 70xxx (70000-70999), which is above the maximum TCP port (65535). The OS refuses to bind those ports, so IsPortAvailable returned false and strict mode reported every prod service as "already in use" — all prod forwards failed while dev (50xxx, valid) worked. - Move the prod band to 60xxx (prod = dev + 10000; same last three digits, only the 50/60 prefix differs). All ports now <= 60402, well within range. - Add multi-env config validation that rejects a localPort outside 1-65535 (and an environment with no context) at load, with a clear message instead of a misleading "port already in use" later. - Update tests (60xxx band + validation) and docs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mk52pPoT73TBHRakrDnGkB
aaronVerones
added a commit
that referenced
this pull request
Jul 3, 2026
The v1.6.0 fix (#47) moved overwatch's dev port to 50030 so all dev ports sit in the 50xxx band. The v1.6.1 prod-band fix (#49) regenerated environments.yaml from default.yaml, which silently reverted overwatch back to 3030. Restore it to 50030. overwatch remains dev-only (dev-specific namespace). Claude-Session: https://claude.ai/code/session_01Mk52pPoT73TBHRakrDnGkB Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.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
1 participant
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.
Bug
v1.6.0's multi-env prod band was 70xxx (70000–70999), which is above the maximum TCP port (65535). The OS can't bind those ports, so
IsPortAvailablereturned false and strict mode reported every prod service as "already in use". Result: with--multi-env, all dev forwards (50xxx, valid) worked and all prod forwards (70xxx) failed — confirmed on a real run (abind()on 70102 raisesport must be 0-65535).Fix
60xxx(prod = dev + 10000; same last three digits, only the50/60prefix differs, e.g.extractor-config-service=50102dev /60102prod). Max port is now60402, well within range.--multi-envnow rejects anylocalPortoutside1–65535(and an environment with no context) at load, with a clear message — so this class of mistake fails fast instead of surfacing as a misleading "port already in use".Verified: 60xxx ports bind cleanly;
go test ./...green.🤖 Generated with Claude Code