Or iPhone one-tap : US: +16468769923,,134156866# or +16699006833,,134156866#
Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 646 876 9923 or +1 669 900 6833 Meeting ID: 134 156 866 International numbers available: https://zoom.us/u/rDfBtpt
Additional communications are posted in #node-testing on the RChain Discord.
What you can expect this week
We would like your help using a new log aggregation tool for nodes running on the network. We will use time in this session to help you get started using RDoctor. Then we will join a test network and walk through a few scenarios.
Please read the RDoctor documentation. We will use this software and tools to support collecting logs from nodes participating in today's testing session. Note, there are no new updates to RChain Doctor since last week. If you used it last week, please use it again. If you'd like to try again, please do . If it's not for your, no worries.
The session key for today is
Note If you used a previous version of RNode, please delete your existing .rnode directory. Most errors experienced using RNode relate to content in the directory from a previous version.
RNode version for this session
Today's version RChain Node 0.7.1 (081f969aea21bdd3d39c7680a8eccf8496ea8f9a)
You best support the improvement and development of the RChain platform when you file a bug to report challenge you faced or unsuccessful outcomes. This will help us collect all relevant information to better understand your setup and experience.
Testing session summary
We did have success collecting logs from some participants. We know the aggregation works. We also observed difficulties running the tool on the user side. We will work to improve the configuration and operation of the tool for next week's testing.
Success in starting a test net
Success in adding peers to the network
Limited success in nodes catching up to the state of the blockchain
Some nodes had the full state
Some nodes added up to 34 blocks and were unable to add more despite seeing new blocks added and requesting missing blocks from peers
Some notes added fewer blocks and were stuck
No success bonding new validators because they were unable to add the block containing their bond
Bootstrap node crashed with out of memory error. Nodes joining the network were able to join and not receive an approved block. Ticket created to add messaging that bootstrap is down.
A validating node received a JustificationRegression error and was not longer able to propose