Appearance
Reporting bugs and sending feedback
Audience: Anyone using meshO Manager who has found a problem, has a question, or has an idea.
How to tell us about a bug, ask a question, suggest a feature, or point out something wrong in these docs. There are two ways in: email and GitHub Issues.
Which one to use
| You want to… | Use |
|---|---|
| Get help with a problem, especially one at an event | |
| Send anything that includes an event backup or competitors' details | |
| Ask a question | |
| Report a bug you can describe without private data | Either — GitHub Issues lets other users see it and add to it |
| Suggest a feature or an improvement | Either — GitHub Issues lets other users vote for it |
| Point out something wrong or missing in these docs | Either |
If you're not sure, email. Nothing is lost by choosing the "wrong" one.
Email
Write to help@mesho.live.
Email is private, so it's the right place for anything that includes an event backup, a log file, or competitors' names and details. It suits questions and urgent problems too.
GitHub Issues
Open an issue at github.com/mesho-live/manager-releases/issues. You need a free GitHub account.
Before opening a new one, search the existing issues: if somebody has already reported the same bug or asked for the same feature, add a comment or a 👍 to theirs. That tells us how many people it affects.
Issues are public
Anyone on the internet can read an issue and anything attached to it. Never attach an event backup, a log file, or a screenshot showing competitors' details to an issue. An event backup holds competitors' personal details and the event's liveresultat upload password. If an issue needs any of these, say so in the issue and email them to help@mesho.live, mentioning the issue number.
Reporting a bug
The more of this you can include, the faster it can be found and fixed:
- What you did, what you expected, and what happened instead. A step-by-step list is best: "Opened the competitor, changed the class to M21E, pressed Save — the status went back to DNS."
- Roughly when it happened. The time helps find it in the log.
- The version, from About in the tray or menu bar.
- Your computer: Windows, Mac or Linux, and which browser if the problem is in a page.
- A screenshot, if the problem is something you can see.
- That day's log file, by email. Troubleshooting says where to find it.
- A backup of the event, by email, if the problem is about an event: Backup event → Download on its card. It includes the event's audit trail, card downloads and radio data, which is usually what's needed to see what happened. See Backup and restore.
If you can make it happen again, say so and how; if it happened once and you can't, say that too. Both are worth reporting.
Suggesting a feature
Tell us what you're trying to do and why, not only the feature you have in mind: "At our carnivals the start team needs to see who is late for their start, so we can call them" says more than "add a late-starters list", and may have an answer that already exists. Say how often it comes up and what you do today instead.