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.
docs/site/troubleshooting.mdsays to readtaskuary.logwhen the app closes on start ("a corruptconfig.tomlis the common one"). But a brokenconfig.tomlraises before anything useful is logged -taskuary.logonly holds its own "log file:" line. The traceback goes:taskuaryfrom pip;~/.taskuary/desktop-error.logfor the desktop app (taskuary/desktop.py, the crash handler inmain) - 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]", thenpython -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.