-
Notifications
You must be signed in to change notification settings - Fork 124
vine: don't print Submitted recovery task xxx to terminal
#4264
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
vine: don't print Submitted recovery task xxx to terminal
#4264
Conversation
dthain
left a comment
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.
I'm thinking that we shouldn't introduce a new API entry point for every little statistic that we would like to return. How about modifying vine_stats instead?
In the past, I would be every loath to break ABI by changing the structure size, but I think everyone is coming through Python now, and it's easier to ensure a match between Python and C.
|
That is a good point! |
|
ready to merge? |
|
RTM |
* vine: don't print Submitted recovery xxx on terminal * trigger rebuild * use stats * restore * no factory display * merge * remove printf * lint --------- Co-authored-by: Jin Zhou <[email protected]> Co-authored-by: Benjamin Tovar <[email protected]>
Proposed Changes
For now, whenever a recovery task is submitted, a message is printed to the user's terminal, which can be distracting.
Users don't need to know about individual recovery tasks or their operations, instead, they only care about the overall progress. If we do want to inform them, only the total number of recovery tasks is relavant
Therefore, we should stop printing
Submitted recovery task xxxto their terminal. Instead, the manager should track the number of recovery tasks submitted, and expose an API for the upper-level graph executor to decide whether or not to display that information.Merge Checklist
The following items must be completed before PRs can be merged.
Check these off to verify you have completed all steps.
make testRun local tests prior to pushing.make formatFormat source code to comply with lint policies. Note that some lint errors can only be resolved manually (e.g., Python)make lintRun lint on source code prior to pushing.