Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Panic when node.nodeMessageChan <- lib.NodeErase message is sent for the first time #413

Open
hackintoshrao opened this issue Nov 6, 2022 · 0 comments · May be fixed by #414
Open

Panic when node.nodeMessageChan <- lib.NodeErase message is sent for the first time #413

hackintoshrao opened this issue Nov 6, 2022 · 0 comments · May be fixed by #414

Comments

@hackintoshrao
Copy link
Contributor

When the message is sent for the first time using node.nodeMessageChan <- lib.NodeErase, it panics. This is because node.IsRunning is false when the message was sent. The value is set at a later point.
hackintoshrao added a commit to hackintoshrao/core that referenced this issue Nov 6, 2022
@hackintoshrao
Bug fix and improves to Node.Start() and Node.Stop()
23ff95d 
- Create Meaningful error macros
- Make IsRunning flag atomic for safety purpose.
- Fix deso-protocol#413
- Add utility functions for change the status of the node.
@hackintoshrao hackintoshrao linked a pull request Nov 6, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bugs fix and improvements to Node.Start() and Node.Stop() hackintoshrao/core
1 participant
@hackintoshrao