Skip to content

rpc: node_info may return nil on start #1199

@melekes

Description

@melekes
When we send a status rpc request via websocket immediately after establishing the websocket connection, node info will may be null while later calls will have a non null node info.

Delaying the call 5+ seconds yields expected results.

Looks like the other reactors are not fully up but rpc is already allowed ?
Does that male sense?

PS tendermint 0.12

Need to check / try to reproduce and fix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C:rpcComponent: JSON RPC, gRPC

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions