Thanks for taking the time to submit a bug report. SpicyNodes is brand new, and we need your help to work out the kinks.
The more detailed your bug report, the easier it will be for us to fix the problem. Here are tips on how to submit an effective bug report.
- Be precise - We will try to replicate the bug, so the more specific you can be, the better
- One bug per report
- No bug is too trivial to report - Small bugs may hide big problems
- Clearly separate fact from speculation
On the "Submit a bug" page, there are several fields. These are all optional, but typically the more complete your report, the greater the chance we can fix it quickly.
- Brief Summary - Provide a descriptive summary of the issue.
- What action were you performing? - What were you trying to do at the time of the bug (if it is not obvious from your summary)? For example, what steps should we take in order to replicate the problem? If you can detail the exact steps needed to replicate the bug, that would be terrific.
- What problem or error message did you see? - If SpicyNodes displayed a message, or you saw unusual behavior, please describe it.
If you have a complex bug, sometimes it is helpful to provide additional information to SpicyNodes engineering. You can add this to the "What problem or error message did you see?" question on the "Submit a bug" page.
- Expected Results - Describe what you expected to happen when you executed the steps above.
- Actual Results - Explain what actually occurred when you executed the steps above.
- Notes - Provide additional information, such as references to related problems, workarounds, and relevant attachments.
If you provide this extra information, please enter it in the "Any other comments?" field.
