Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

If you are participating in community Node testing, you may run into a situation where you see a bug, but you aren't quite sure.  This page will try to help clarify if you are seeing a real issue or not.

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.  

This page will strive to outline what a bug looks like, and where you should file it.


What to include in the ticket:

  1. Summary = Brief statement of what the issue is. Ex: 'Can't connect to network'
  2. Project = CORE
  3. Type = BUG
  4. Priority: 
    1. Highest → Blocks use of a feature
    2. High → Feature very hard to use, difficult workaround
    3. Medium → Feature hard to use, moderate workaround
    4. Low → Feature is unpleasant to use, no workaround
    5. Lowest → Feedback, no fix required.
  5. Description:
    1. Symptom of the problem with a bit more detail
    2. What you expected to happen
    3. Steps to reproduce.  Include as much information as possible.  Such as:
      1. System information (OS, hardware)
      2. Network information (router config if you know it, router type, number of routers, etc..)
      3. What you did.  Step by Step
      4. What happened as you did each step
      5. Any logs from the system (you can ask where the logs are on the system) 

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.


  • No labels