Report a bug

If you found a problem, this page is the support channel. We read the reports, and we don’t promise a reply. When a report describes a bug worth fixing, the fix appears in a later version, and a good report is what gets it there.

Where to report

Email the support address on the imprint page with the subject prefix [bug].

What to include

1. Give your platform and app version, for example “Windows 11, Totsum 0.1.0”. The version is shown in Help → About.
2. Give your hardware, meaning the GPU model and VRAM, or the Mac model and memory.
3. Describe what you did, that is the question you asked and the shape of the data (file format, roughly how many rows and columns, column types). Please don’t send the data itself if it’s sensitive. A description or a small anonymized sample is enough.
4. Describe what happened vs. what you expected. Include error messages verbatim, and screenshots of the Query Flow if the query was wrong. Check first that you can share what they show, as the note below explains.
5. Say whether you can reproduce it, and whether it happens every time.

A note on wrong answers

If an answer looks wrong, the most useful things to send are a screenshot of the Query Flow and, if possible, the generated SQL, which is one click away in the app. They show exactly where the interpretation diverged from your intent.

Check them before you send them. Both can carry pieces of your data, such as table and column names, filter values, row counts and sample rows. If the data is confidential, make sure that you are allowed to share what the screenshot shows, or redact it first. A plain description of the steps can be enough.

Security issues

If you believe you found a security vulnerability, don’t use the bug channel. Email security@totsum.app instead, and please give us reasonable time to fix it before publishing details. The security page says what to include, and it is where advisories are published.