-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
feat: turbo info
command for debugging
#9368
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Skipped Deployments
|
turbo info
command for debugging
@@ -475,9 +475,7 @@ impl Args { | |||
} | |||
} | |||
|
|||
/// Defines the subcommands for CLI. NOTE: If we change the commands in Go, |
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.
Unrelated, but saw it mentioning Go so ✂️
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! Just a couple notes
NoCurrentExe(#[from] io::Error), | ||
} | ||
|
||
pub async fn run(base: CommandBase) -> Result<(), Error> { |
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.
ITG (non blocking follow up): Separate the data from the display logic to make this more unit-test friendly and support additional output formats like JSON.
Something like:
struct TurboInfo {
package_manager: String,
daemon_status: String,
...
}
And then have turbo_info.print()
to actually write the data to stdout
Opting to not print the env vars. If we feel like we need it later, we can print them with an optional flag. |
Description
A command to provide debugging information for reproductions or otherwise understand a machine better. Output will look something close to this.
Testing Instructions
Try it out!