feat: tradingview logging level configuration #436
Merged
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
|
Thanks @azorpax I will merge and release. |
|
Good job @azorpax |
SardorAbdullaev
added a commit
to SardorAbdullaev/binance-trading-bot
that referenced
this pull request
Aug 16, 2022
This reverts commit 526eda9.
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.
Description
This will allow to configure the logging level of the tradingview container by passing an environment variable "TRADINGVIEW_LOG_LEVEL". the accepted values for log level can be viewed here: https://docs.python.org/3/howto/logging.html#logging-levels
Related Issue
#435
Motivation and Context
To be able to configure the logging level of tradingview
How Has This Been Tested?
Tested in my local machine
Screenshots (if appropriate):