fix(cli): running the cli with --debug does not print stack traces #28669
Conversation
But that's what debug is for, printing traces with sourcemap. So let's just always enabled tracing when debugging.
mrgrain
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
kaizencc
temporarily deployed
to
test-pipeline
GitHub Actions
Inactive
There was a problem hiding this comment.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.
aws-cdk-automation
added
the
pr/needs-cli-test-run
mrgrain
added
pr-linter/exempt-test
|
➡️ PR build request submitted to A maintainer must now check the pipeline and add the |
aws-cdk-automation
added
the
pr/needs-cli-test-run
kaizencc
added
pr-linter/cli-integ-tested
aws-cdk-automation
dismissed
their stale review
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
--debugexists for exactly one purpose: Printing source-mapped traces so we can find the code that is going wrong.Let's always enabled tracing when debugging.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license