Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

show state immediately after neo-node start error #762

Closed
cloud8little opened this issue Mar 16, 2021 · 2 comments · Fixed by #763
Closed

show state immediately after neo-node start error #762

cloud8little opened this issue Mar 16, 2021 · 2 comments · Fixed by #763

Comments

@cloud8little
Copy link
Contributor

693f6484b79cc5ba0e9412e90545b98

a806ba04ee24181d0d74fe57bd80fbf

It is caused by the change #758, localnode is null at this time.

after several seconds later, it shows numbers.
@shargon
Copy link
Member

shargon commented Mar 16, 2021

Revert #758?

@bettybao1209 bettybao1209 mentioned this issue Mar 16, 2021
Merged
@ZhangTao1596
Copy link
Contributor

Revert #758?

If you have better solution to solve neo-project/neo#2380.
I found that if you start node with websockt port occupied by another application, you will get different localnodes before and after call NeoSystem.StartNode.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix localnode null bettybao1209/neo-node
3 participants
@shargon @ZhangTao1596 @cloud8little