algorand / algorand/go-algorand

a bug when using command prints status for all nodes in a deployed private network

Abierto
#898 1 comentario 0 reacciones 1 asignado Reclamado por @tsachiherman Ver en GitHub
external contribution
Lenguaje dominante
Go
Estrellas
1.4k
Forks
537
Merge medio
1 d 7 h
PR fusionados (30 d)
18

Descripción

### Subject of the issue
different results when using command prints status for all nodes in a deployed private network. just because stopped one node in network.

### Your environment
* Software version: `2.0.65103.dev [master] (commit #30779007+)`
* Operating System details: macOS

### Steps to reproduce
step1 ` goal network create -r ~/net1 -n private -t genesis.json`
step2` goal node clone -d ~/net1/Primary -n -t ~/net1/NewNode`
step3` goal network start -r ~/net1`
step4` goal node stop -d ~/net1/NewNode`
step5 `goal network status -r ~/net1`

### Expected behaviour
tell all nodes status even though stopped one node

### Actual behaviour
results are random

here is my [genesis.json](https://paste.ubuntu.com/p/qm9DyXHQ58/)
and my [logs](https://paste.ubuntu.com/p/rdJ27zxfPC/)

https://github.com/algorand/go-algorand/blob/307790071c8afb6c785f8e244785a856bca11a58/cmd/goal/network.go#L176-L195

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.