You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
seratch
changed the title
Do we expect the logger passed in App() to be the same logger from action listener?
Respect the configuration of logger parameter across App/AsyncApp loggers
Mar 18, 2022
The logger in the App/AsyncApp constructor is supposed to be used only for logging inside the bolt-python framework. For simple use cases, we have been suggesting to configure logging level at root level and it works for bolt-python apps. However, indeed, this is not intuitive and less flexible.
I just submitted a pull request #618 fixing this issue, which resolves the issue reported here. The change will be released shortly.
When I pass in a custom logger into App(), I am expecting that logger from
def home_tab_opened
listener is the samelogger
asnew_logger
.Reproducible in:
The
slack_bolt
versionPython runtime version
OS info
sw_vers did not work as a built the container from Docker using this image
FROM python:3.9
Steps to reproduce:
(Share the commands to run, source code, and project settings (e.g., setup.py))
Expected result:
I expect the Logger passed in App() is the same logger the framework passes use to the listener function
Print would show
Actual result:
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: