Table of contents
| Table of Contents | ||
|---|---|---|
|
Overview
Each week we invite community members to help test RNode.
- When - Tuesdays at 14:00 UTC
- Where - This meeting takes place online using Zoom
- Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/134156866
- 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 RChaing Discord.
What you can expect this week
We will be tracking down a bug in the communication layer. Testers can expect to instantiate a node and capture diagnostic information in Jira to help the team track down an issue related to communications.
Prerequisites
Ability to build and run RNode using binary installation packages available in https://repo.pyr8.io/rchain/downloads/dev/
or
Ability to build and run RNode from this Docker image
| Code Block |
|---|
docker pull rchain/rnode:dev |
Ability to file a bug
This will help us collect all relevant information to better understand your setup and experience.
Download of the bonds.txt file. https://repo.pyr8.io/rnode-test-sessions/bonds.txt
Pick out a row with validator key pair. https://docs.google.com/spreadsheets/d/18merD3OzaDk7nmxQ78SUZBzWLbxA-aOnmcdxpXrp_U0/edit#gid=0
Specify your node info if you want. You can wipe your information after testing.
Participants
- Alexander Guryev
- Glen Braun
- Ian Bloom
- Jake
- Mateusz Probachta
- Matthew Kaye
- Paolo DoOnorio De Meo
- Will Qui
- Deanna Duke
- Dror
- Ed Eykholt
- Felix Lutsch
- Lee Carter
- Nuno Lopes
- Pawel Szulc
- Seth Bailey
- Luigi Demeo
- Chibuike David Asamonye
- Jamie Cook
- Jim Whitescarver
Bugs filed
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Chat log
| View file | ||||
|---|---|---|---|---|
|
Testing session summary
Community testers help test the networking of RNode. Testers were asked to file bugs in Jira to share their experiences. These are the themes that emerged:
- Networking blockers for RNode operators using Docker - One user had success adding port forwarding to the node command in order to connect to bootstrap
- RNode hangs while writing files - Several users experienced this
- Nat busting will be an issue for many operators with the current state of RNode
- Users need support reviewing their configurations related to RNode operation