Filing a bug

If you are participating in community RNode testing, 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.

Guidelines:

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.

First check to see if the bug is already reported

Bugs are shown on this dashboard: https://rchain.atlassian.net/secure/Dashboard.jspa?selectPageId=10104
If you see your experience already in a bug, please add information in comments.

Where to file an issue

If you don't see your bug listed on the dashboard, or are uncertain if a bug listed is the same, err on the side of caution and file a new bug.

Please go to https://rchain.atlassian.net
Either log in or create an account. If you choose not to do this, please do add your name and contact information to the ticket, so we can follow up if needed.

Select + to create a new issue

What to include in the issue

Project = CORE
Issue type = BUG
Summary = Brief statement of what the issue is. Ex: 'Can't connect to network'
Description:
- Symptom of the problem with a bit more detail
- What you expected to happen
- 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
  - What happened as you did each step
  - 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 pastebin and share the link or save as a file and add as an attachment.

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:

My node gets the same block over and over again
The block in the fork choice rule doesn't match the latest block proposed in a small group of nodes
Unable to call a name that has been deployed to a block or reference a contract on the blockchain.