slackapi / slackapi/bolt-python
Make Exeption traceable in lazy listener
@seratch 已经在做这个了。
开始于 2022年4月20日。
- 主要语言
- Python
- 星标
- 1.3k
- 派生
- 288
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 10
描述
(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.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。