Skip to content

Reject invalid server ports before startup - #80

Open
1cbyc wants to merge 1 commit into
ldbumble:masterfrom
1cbyc:1cbyc/69-validate-ports
Open

1cbyc wants to merge 1 commit into
ldbumble:masterfrom
1cbyc:1cbyc/69-validate-ports

Conversation

@1cbyc

@1cbyc 1cbyc commented Sep 26, 2026

Copy link
Copy Markdown
Contributor

What & why

Validate CLI and environment port values before they reach the socket layer. Out-of-range --port values now produce a normal argparse usage error, while invalid TASKUARY_PORT overlays are ignored with a clear warning so unrelated commands can still load configuration.

Fixes #69

Checklist

  • python -m pytest -q passes (5,364 passed, 10 skipped, 177 subtests)
  • New behavior has focused CLI and environment tests
  • UI not touched
  • README not needed; existing valid-port behavior is unchanged

Co-authored-by: insisong emmanuelisaacnsisong@gmail.com

Co-authored-by: insisong <emmanuelisaacnsisong@gmail.com>

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

An out-of-range or non-numeric port gives a raw traceback

1 participant