-
Notifications
You must be signed in to change notification settings - Fork 35
Use batch_info v2 in mobile_config_cli #971
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
Conversation
mobile_config_cli/src/client.rs
Outdated
| Ok(()) => Some(res), | ||
| Err(_) => None, | ||
| Err(e) => { | ||
| eprintln!("Response verification failed. {e}"); |
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.
| eprintln!("Response verification failed. {e}"); | |
| tracing::error!(?err, "Response verification failed"); |
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.
do these tracing logs get output to the terminal stdout normally when operating the commands since this is in the context of an actual CLI (not just a clap construct for launching a server process) @michaeldjeffrey ? This seems like the one place where println! and eprintln! would be appropriate
jeffgrunewald
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.
Looks good to me, assuming the custom tracing and tracing crate operations will output to a cli terminal as we would expect since we're in a foreground process operating directly with the application
* Print error if verification failed * Use v2 requests * Use tracing::error to print error message * Add DeploymentInfo
* Print error if verification failed * Use v2 requests * Use tracing::error to print error message * Add DeploymentInfo
No description provided.