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

Troubleshooting: "it started and immediately closed" points at a log that never has the crash

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
documentation

Research direction

Edit docs/site/troubleshooting.md, starting with the section for an app that starts and immediately closes and the “Where the logs are” table. Read taskuary/desktop.py and its crash handler in main to confirm the desktop log location. Done means the page names terminal output for the pip command, ~/.taskuary/desktop-error.log for the desktop app, and lists desktop-error.log in the table; no test is required.

Written by the indexing model from the issue text.

Description

documentation good first issue

docs/site/troubleshooting.md says to read taskuary.log when the app closes on start ("a corrupt config.toml is the common one"). But a broken config.toml raises before anything useful is logged - taskuary.log only holds its own "log file:" line. The traceback goes:

  • to the terminal, when you started it with taskuary from pip;
  • to ~/.taskuary/desktop-error.log for the desktop app (taskuary/desktop.py, the crash handler in main) - a file no page mentions.

Done when that section names both places, and the "Where the logs are" table lists desktop-error.log.

Test - none needed for the docs. Bonus: a test that the desktop crash handler writes desktop-error.log (point the home directory at a temp folder).

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.