-
Notifications
You must be signed in to change notification settings - Fork 71
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
Short Discussions don't work with JSON payloads #73
Comments
Yes, just start from terminal with
|
The original stack trace comes from the Redis session driver, so that would be a good thing to look into. It sounds like somewhere in the user data structure, it's storing a data type that isn't JSON-serializable (looks like a regexp object). I don't know off-hand what that data could be; To debug it I'd get as close as possible to where the exception is raised, and |
I try to the reproduce the issue but it doesn't throw me an error. I don't know which parts of the program require Flask/Redis session driver, as you mentioned. Can someone help explain further? Thank you. Here is what do in my local machine. I prepare a script file
Below is the call and the response.
|
By default RiveScript stores all user variables and state in memory, the bug exists when using Redis cache to store user variables. Here is my flask app as an example with Redis as session storage. Short discussions won't work with it as it would store something that is not JSON-serializable. N.B.- I used redis_storage.py from eg/sessions/
|
@Dinh-Hung-Tu @kirsle How is the progress using |
The error raises wether I communicate to the bot by invoking the interactive mode with the
--json
(or-j
) flag or running flask app accessible via a JSON endpoint.Edit/fixed the post formatting. --Kirsle
The text was updated successfully, but these errors were encountered: