READ THIS BEFORE POSTING YOUR ISSUE

[iabaako]

Thank you for engaging with the Datasure team. We care about responding to your issues promptly. Help us by opening high quality issues, identifying related issues and avoiding duplication of issues.

When to open a new issue

Before opening a new issue, search for a similar issue. GitHub's search is frequently unreliable, we struggle to find issues we know exist, so we understand if you have a hard time finding an existing issue.

If you find a similar issue, confirm that your issue is the same. If you are not certain if your issue is the same, it is best to create a new issue instead. Including a link to possible existing issues can save us a lot of time. Some error messages can look similar, but we often need more information to help diagnose your issue and it's best to avoid side-tracking an existing discussion.

If your request or problem is the same as an existing issue, upvote the original post with a 👍 instead of adding a comment like "+1" or "I'm encountering this too". If you do comment, make sure you're adding new context to the conversation.

What should be included

When reporting a problem or asking a question, be sure to include the following:

• The version of Datasure. You can get this with the command datasure --version
• The operating system
• Images or videos where applicable
• The output on your terminal. Start datasure with the command datasure --logging debug to get a more verbose output if necessary.
• Take some time to describe how the issue can be reproduced.

Including this information can save a lot of back and forth and we'll be able to solve your problem faster.

A few things to keep in mind:

• If you're not on the latest version of Datasure, make sure that your issue is still present on the latest version.
• If the behavior worked on a previous version of Datasure and regressed in a new version, please share all the versions you have tested. This can help track down the cause of the bug.