-
-
Notifications
You must be signed in to change notification settings - Fork 278
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.
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
lodecli beacon init / run #842
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
👍
} | ||
|
||
process.on("SIGTERM", cleanup); | ||
process.on("SIGINT", cleanup); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should use https://github.com/jtlapp/node-cleanup/blob/master/node-cleanup.js as it handles all signals and exceptions
Looks great. Do we want to start moving some e2e tests to lodecli? |
@tuyennhv Yes! I'll add the beacon e2e test. (and update lodecli to include the work in #843) |
I added some sanity unit tests, but the beacon node is currently not stable enough to run in a meaningful e2e test. I'll make an issue for this |
No description provided.