-
Notifications
You must be signed in to change notification settings - Fork 235
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
Rasa SDK incompatible with Sanic version 21.12.0 #647
Comments
Thank you for this detailed issue @khalidtwl . You are right as far as I can see and we have similar problem (and a little more) with For this ticket I think the solution could easily be explicitly specifying Sanic app name instead of getting it from the module name. Sanic apps are not created in many places and hence we do not need naming like loggers. |
@tayfun can we close this? |
@donodje can we close this issue? |
Rasa version: 1.10.5
Rasa SDK version: 3.0.2
Python version: 3.7.1
Operating system (windows, osx, ...): linux
Issue: Sanic's latest version 21.12.0 release includes several deprecations, the most notable of which involves replacing a "warn" message with an exception in the
sanic/base/root.py
file (line 37) if the name passed into the Sanic constructor does not match their regex. Sanic is now enforcing that names have only alphanumeric, underscore, or dash characters.This is an issue because in the Rasa SDK's
endpoint.py
line 77, it passes in__name__
into the Sanic constructor, which israsa_sdk.endpoint
and fails the Sanic checks due to it containing a.
character. This results in asanic.exceptions.SanicException
and our custom Action Server failing to start.According to the project dependencies, there is a Sanic version constraint of "^21.6.0" which allows Sanic version "21.12.0" to be used despite their incompatibility. Downgrading our Sanic version resolved this issue.
Error (including full traceback):
Command or request that led to error:
Definition of done
rasa.server
) to a clear name without dots (eg.rasa_server
) for rasa-sdkThe text was updated successfully, but these errors were encountered: