-
Notifications
You must be signed in to change notification settings - Fork 45
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
zk lightnet logs command implementation. #520
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.
Great work @shimkiv! I approved this, but I have a question and some suggestions. I will leave it up to you if you want to implement the suggestions or not.
Co-authored-by: Yoni Mekuria <[email protected]>
Co-authored-by: Yoni Mekuria <[email protected]>
Co-authored-by: Yoni Mekuria <[email protected]>
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.
Nice refactor!
zk lightnet logs save
command does not provide any selection options, because usually it is good idea to grab all relevant logs at certain point in time.zk lightnet logs follow
command, on the contrary, gives users an option to follow the logs of certain processes, well, because you can't simply follow several files without introducing additional complexity (logs from different sources pre-processing) and a bit of mess when you will also need to distinguish which entries are from what processes.Closes #502
As per the RFC.