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
TypeError: MiddlewareSet.receive_activity_internal.<locals>.call_next_middleware() takes 0 positional arguments but 1 was given
The text was updated successfully, but these errors were encountered:
heyitsaamir
added
bug
Indicates an unexpected problem or an unintended behavior.
needs-triage
The issue has just been created and it has not been reviewed by the team.
labels
Dec 18, 2024
heyitsaamir
changed the title
Typing for Middlware is incorrect
Typing for Middleware is incorrect
Dec 18, 2024
- Adds a middlware for memory_module. Now, whenever a message from a
user comes in, or message is sent from the agent out back to the user,
it's automatically captured by the supplied memory_module.
Discovered a number of bugs in botframework-python. Added them:
microsoft/botbuilder-python#2197microsoft/botbuilder-python#2198
Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
4.16.2
Describe the bug
The typing for the middleware on_turn handler is:
botbuilder-python/libraries/botbuilder-core/botbuilder/core/middleware_set.py
Line 27 in a7f5d91
Notice the arguments is a
TurnContext
?However, it's called like:
botbuilder-python/libraries/botbuilder-core/botbuilder/core/middleware_set.py
Lines 83 to 89 in a7f5d91
Here
call_next_middleware
takes no arguments.This results in:
The text was updated successfully, but these errors were encountered: