Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open Beginner friendly
  • Is something wrong?
#69 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
cli

Research direction

Start with taskuary/cli.py for the --port argument and taskuary/config.py for _env_server. Run the focused cases in tests/test_config.py, then python -m pytest -q. Done means ports outside 1-65535 produce argparse's exit code 2 and an invalid TASKUARY_PORT no longer raises, instead following the issue's requested warning or clear-error behavior.

Written by the indexing model from the issue text.

Description

bug good first issue

--port is type=int with no range check, and TASKUARY_PORT is read with a bare int():

taskuary --port 70000              -> OverflowError: connect_ex(): port must be 0-65535
TASKUARY_PORT='8080x' taskuary     -> ValueError: invalid literal for int()

config.load() runs for every command, so a bad environment variable breaks all of them.

Where: taskuary/cli.py (the --port argument), taskuary/config.py (_env_server).

Done when argparse rejects a port outside 1-65535 with a normal usage error (exit code 2), and a bad TASKUARY_PORT is ignored with a logged warning (or refused with one clear line).

Test - tests/test_config.py: _env_server() with TASKUARY_PORT='abc' does not raise; parsing --port 70000 raises SystemExit with code 2.

Getting started: pip install -e ".[dev]", then python -m pytest -q (offline, a few seconds). UI work: cd website && npm ci && npm test. See CONTRIBUTING.md. One small PR with the change and its test is perfect.

Dominant language
Python
Stars
116
Forks
22
Avg merge
1d 9m
Merged PRs (30d)
11

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ldbumble/taskuary

All issues in ldbumble/taskuary

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.