If you are participating in community RNode testing, using the public testnet, the sandbox testnet or running your own node or network, you may run into a situation where you see a bug or have an experience that is inconsistent with what you expect. Use the information on this page to file a bug so the development team has a record of your experience.
...
If you are expecting the software to do something in a particular way and it doesn't, you should file an issue and let us know how the software failed to meet your expectations. These are referred to a 'usability issues'. These are a great form of feedback for the development team. Their value should not be underestimated.
...
What to include in the issue
- Project = CORERCHAIN
- Issue type = BUG
- Summary = Brief statement of what the issue is. Ex: 'Can't connect to network'Hint: a cut/paste of the error message is helpful
- Description:
- Symptom of the problem with a bit more detail
What you expected to happen
Please include all of the following information in the description field. - What version of RNode were you running?
- Steps to reproduce. Include as much information as possible. Such as:
- System information (OS, hardware)
- Network information (router config if you know it, router type, number of routers, etc..)
- What you did. Step by Step
- Observations
- What happened as you did each step?
- What did you expect to happen?
- Any logs from the system (you can ask where the logs are on the system)Log information - Share all of the log information you can. If it's lengthy, consider adding logs to or contracts deployed. You can provide information via pastebin and share the link or save as a file and add as an attachment.
- Questions or ideas
- Based on the scenario and observations what questions do you have?
- Based on the scenario and observations what ideas or recommendations do you have?
| |
- Priority:
- Highest → Blocks use of a feature
- High → Feature very hard to use, difficult workaround
- Medium → Feature hard to use, moderate workaround
- Low → Feature is unpleasant to use, no workaround
- Lowest → Feedback, no fix required.
- Note: There are other fields on the ticket template. You do not need to add information to these fields.
- Select Create when done.
| |
Communications:
Here is a list of possible symptoms that are communications issues
- My node tells me it is connected, but I don't see any of the effects of being connected to the network.
- I don't receive blocks that have been proposed by other nodes
- My list of peers isn't growing.
- The server console isn't showing anything.
- My node tells me it can't find the bootstrap node and exits
Consensus:
Here's some things that could go wrong:
...
- Note: There are other fields on the ticket template. You do not need to add information to these fields.
- Select Create when done.
|  Image Added
|
