Fix KeyError: 'TERM' when no TERM exist #3
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- There is no TERM variable called from script in docker guest. It cause KeyError: 'TERM'. Signed-off-by: Hiroshi Miura <miurahr@linux.com>
|
LGTM. Thanks for the patch @miurahr merging now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is no TERM environment variable if CLI is called from python script in docker container.
It cause
KeyError: 'TERM'because it does not check an environment variable existence.Signed-off-by: Hiroshi Miura miurahr@linux.com
Signed-off-by: Hiroshi Miura miurahr@nttdata.co.jp