Skip to content
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

Make Exeption traceable in lazy listener #635

Open
3 tasks
jimmymaise opened this issue Apr 20, 2022 · 2 comments
Open
3 tasks

Make Exeption traceable in lazy listener #635

jimmymaise opened this issue Apr 20, 2022 · 2 comments
Assignees
Labels
Milestone

Comments

@jimmymaise
Copy link

jimmymaise commented Apr 20, 2022

(Describe your issue and goal here)
Currently, using lazy listener for FAAS (such as AWS Lambda), it's really difficult to debug. If we have a exception, we just have something like

Failed to run an internal function (Exception ABC)

We don't know exactly, what is the error, traceback, error line etc...

 try:
            await internal_func(
                **build_async_required_kwargs(
                    logger=logger,
                    required_arg_names=arg_names,
                    request=request,
                    response=None,
                    this_func=internal_func,
                )
            )
        except Exception as e:
            logger.error(f"Failed to run an internal function ({e})")

So should we have an option to enable the exception traceback or provide some meaningful error information to debug instead of just simply message like that

On the other hand, the document about error handling does not work with lazy listener so we also need to update.
https://slack.dev/bolt-python/concepts#errors

Category (place an x in each of the [ ])

  • slack_bolt.App and/or its core components
  • slack_bolt.async_app.AsyncApp and/or its core components
  • Adapters in slack_bolt.adapter
  • [x ] Others

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.

@jimmymaise jimmymaise changed the title Make Exeption traceable in lazy listion Make Exeption traceable in lazy listener Apr 20, 2022
@seratch seratch added this to the 1.x milestone Apr 20, 2022
@seratch seratch self-assigned this Apr 20, 2022
@seratch
Copy link
Member

seratch commented Apr 20, 2022

Hi @jimmymaise, thanks for the feedback. We will look into this. This can be improved in future versions and/or needs to be clearly mentioned in the documents.

@ddhanak
Copy link

ddhanak commented Aug 18, 2022

We are facing the same issue as @jimmymaise, I think it would be helpful to have the exception traceback (we are using sentry and would love to see what line is causing the issue).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants