Nexstrata

Beta

Report a bug

Found something broken or behaving unexpectedly? Filing an issue on GitHub is the fastest way to get it fixed.

Before you file

Check whether someone already reported it:

  1. Go to github.com/skyfly200/data-map/issues
  2. Search for a few words that describe what went wrong — a duplicate report is more noise, not more signal.

If you find an existing issue that matches, add a 👍 reaction to it. That tells us how many people are hitting the same problem, which helps with prioritization.

Filing a new issue

Open a New Issue and fill in:

What happened

Describe what you saw. Be specific: "the Charts page showed a blank screen" is more useful than "something is broken".

What you expected to happen

One sentence is enough.

Steps to reproduce

A numbered list of what you clicked or typed before the problem appeared. If you cannot reproduce it reliably, say so — a flaky bug is still worth reporting.

Environment

  • Browser and version — e.g. Chrome 126, Safari 17, Firefox 128
  • Device — desktop, phone, tablet
  • Operating system — e.g. macOS 14, Windows 11, iOS 17
  • Dataset in use — if the bug only happens with a specific species or dataset, include its name

Screenshot or recording (optional but very helpful)

A picture of a broken UI makes a report 10× faster to diagnose. Most browsers let you take a screenshot with Cmd+Shift+4 (Mac) or Win+Shift+S (Windows).

What happens next

Issues are reviewed regularly. You will get a comment when:

  • The report is confirmed and a fix is planned
  • More information is needed before it can be investigated
  • It is a known limitation rather than a bug, with an explanation of why

You do not need an account to open an issue. GitHub accounts are free and let you get notified when your issue is updated.

Feedback that is not a bug

  • Feature request — something the app does not do yet that you wish it did: open an issue with the label enhancement
  • Question — not sure if it is a bug or you are doing something wrong: open an issue with the label question, or reach out through the community channels listed on the project page