Repository navigation
Fixed fetching of names for callable objects (#215) - #216
Conversation
Added new function name_for_callable() in util.utils. Fixed name properties for CustomMiddleware and AsyncCustomMiddleware to use the new function. Modified listener/thread_runner.py and listener/asyncio_runner.py to use the new function to name lazy functions. Added test cases for middleware and lazy function cases.
|
Thanks for the PR @nickovs! 🎸 When you have a moment, would you mind signing the CLA so that we can merge your work? It's quick and digital, just select the link from the CLAssistant. In the meantime, we'll review it and let the CI run the tests 🙂 |
|
@mwbrooks I have signed the CLA. There seems to be a bug in your CLA assistant. There are two different email addresses in my commits (one home, one work). Both are linked to my GitHub account and the commit history for my branch correctly shows both commits as belonging to the @nickovs user, but for some reason the CLA Assistant is only showing one identity as having signed the CLA. When I click on the link to sign it again it says that I have already signed the CLA and won't let me Sogn it again. |
|
@nickovs Could you squash them into one commit using the email address used for signing the CLA? |
Added new function name_for_callable() in util.utils. Fixed name properties for CustomMiddleware and AsyncCustomMiddleware to use the new function. Modified listener/thread_runner.py and listener/asyncio_runner.py to use the new function to name lazy functions. Added test cases for middleware and lazy function cases.
…on into middleware-class-names
|
OK. I did a |
|
@nickovs Thanks for promptly submitting this PR! I am going to check this in detail later today (I live in +09:00 timezone). One thing, it seems the following tests for adapters fro AWS Lamdba are failing. Have you already checked this out? |
|
@seratch Regarding the tests, I just noticed that. When I run the tests locally, whether on the main branch or on my new code, several of the tests are very unreliable, frequently failing with |
Yes ... this is a known issue that happens on local machine. #157 Re-running the same tests by |
|
Actually it was just a dumb cut-and-paste error. I've pushed a fix. I added type hints to the new |
Codecov Report
@@ Coverage Diff @@
## main #216 +/- ##
==========================================
+ Coverage 91.61% 91.62% +0.01%
==========================================
Files 159 159
Lines 4760 4767 +7
==========================================
+ Hits 4361 4368 +7
Misses 399 399
Continue to review full report at Codecov.
|
|
Thanks - LGTM |
Added new function name_for_callable() in util.utils.
Fixed name properties for CustomMiddleware and AsyncCustomMiddleware to use the new function.
Modified listener/thread_runner.py and listener/asyncio_runner.py to use the new function to name lazy functions.
Added test cases for middleware and lazy function cases.
This addresses the issue in #215.
Category (place an
xin each of the[ ])slack_bolt.Appand/or its core componentsslack_bolt.async_app.AsyncAppand/or its core componentsslack_bolt.adapter/docsRequirements (place an
xin each[ ])Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
./scripts/install_all_and_run_tests.shafter making the changes.