We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
import feast logging.basicConfig(level=level, format=FORMAT) logging.error("msg")
should print logging message according to FORMAT
FORMAT
It uses the format defined in feast at the module level.
feast
Same as in "Expected Behavior"
I see that basicConfig is called here:
basicConfig
feast/sdk/python/feast/cli.py
Line 84 in c9eda79
feast/sdk/python/feast/__init__.py
Line 30 in 0ca6297
If there are any other entry points that need to set up logging, they should call the function, but the call in __init__.py must be removed.
__init__.py
The text was updated successfully, but these errors were encountered:
I think you're right @elshize - good catch. Would you be willing to submit a PR for this? :)
Sorry, something went wrong.
Actually I'm going to quickly fix this so that we can include the fix in the release we're planning on cutting tomorrow.
@achals Thanks. Sorry I didn't reply sooner, it was nighttime here :)
achals
Successfully merging a pull request may close this issue.
Expected Behavior
should print logging message according to
FORMAT
Current Behavior
It uses the format defined in
feast
at the module level.Steps to reproduce
Same as in "Expected Behavior"
Specifications
Possible Solution
I see that
basicConfig
is called here:feast/sdk/python/feast/cli.py
Line 84 in c9eda79
feast/sdk/python/feast/__init__.py
Line 30 in 0ca6297
If there are any other entry points that need to set up logging, they should call the function, but the call in
__init__.py
must be removed.The text was updated successfully, but these errors were encountered: