Found a bug? Tell us.
Volpi is in beta, so things will break. A clear report lets us find the problem and fix it. Here is how to write one.
Check that it is not already known.
Some limits of the beta are already listed. Someone may also have reported your bug. If they have, add your details to their report instead of opening a new one.
Note your setup.
We need to know which Volpi and which computer.
- Your Volpi version. It is shown in the update log on the Home screen.
- Your operating system and its version, for example Fedora 44 or Ubuntu 24.04.
Make it happen again.
A bug we can repeat is a bug we can fix. Try it once more and write down exactly what you did.
- The steps, one by one, from opening Volpi.
- What you expected to happen.
- What happened instead. Copy any error message word for word.
- Whether it happens every time, sometimes or only once.
Keep your research private.
Bug reports are public. Your research does not belong in them.
- Do not attach your own files, participant data or personal details.
- If a file is needed to show the bug, make a small example instead.
- Check screenshots before you add them.
Open the report on GitHub.
Pick the form that fits. It asks for everything above, one box at a time. You need a free GitHub account.
Thank you. Every report makes the beta a little less beta.