-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Terminal size is 0 on CI and so diff and deploy throws exception when trying to create table of changes #2253
Terminal size is 0 on CI and so diff and deploy throws exception when trying to create table of changes #2253
Comments
This isn't really an issue with cdk it is an issue with combining the library that cdk uses with certain CI environments. The CI environment reports |
Still feels like a bug m |
Fair enough. Shout if you need any logs, configs, etc. |
Thanks for reporting! |
On some CI systems the terminal width is reported as 0 (instead of "unknown"), which causes table formatting to fail. Enforce a minimum terminal width. Fixes #2253.
On some CI systems the terminal width is reported as 0 (instead of "unknown"), which causes table formatting to fail. Enforce a minimum terminal width. Fixes #2253.
On some CI systems the terminal width is reported as 0 (instead of "unknown"), which causes table formatting to fail. Enforce a minimum terminal width. Fixes aws#2253.
On some CI systems the terminal width is reported as 0 (instead of "unknown"), which causes table formatting to fail. Enforce a minimum terminal width. Fixes aws#2253.
I use - run:
name: diff
command: |
stty rows 64 cols 204
npx cdk diff --app "npx ts-node bin/A.ts" Just FYI for CircleCI and cdk user. |
Describe the bug
In some CI setups (CircleCI and Jenkins), process.stdout.column can return 0 and so when the cdk uses the table library to create the table of resources to print to logs it throws an exception as terminal width cannot be 0.
To Reproduce
Run any cdk diff or cdk deploy command on a terminal with 0 width or on a CI setup where process.stdout.column returns 0
CI Logs
https://circleci.com/gh/CSmither/aws-cdk-demo/30
Expected behavior
Print a table of the stack to logs and continue on to either describe diff or deploy stack
Version:
Notes
Stack overflow post just to link them
The text was updated successfully, but these errors were encountered: