search

RasaHQ / rasa

💬 Open source machine learning framework to automate text- and voice-based conversations: NLU, dialogue management, connect to Slack, Facebook, and more - Create chatbots and voice assistants
https://rasa.com/docs/rasa/
Apache License 2.0
18.94k stars 4.64k forks source link

Logging Error when non ascii character is used in intent name #3088

Closed varshakirani closed 5 years ago

varshakirani commented 5 years ago

--debug flag in rasa_core.run throws log UnicodeEncodeError for intent names having nonascii characters.

varshakirani commented 5 years ago

image

akelad commented 5 years ago

Thanks for raising this issue, @erohmensing will get back to you about it soon.

erohmensing commented 5 years ago

@akelad lol this is varsha

akelad commented 5 years ago

hahaha i didn't realise. is this an actual bug then or is it related to a specific OS/setup?

erohmensing commented 5 years ago

good question, i don't think anyone's tried to replicate it yet. i know i got a similar error ~on my OS~ in jupyter notebooks when processing the movie_dialog dataset though

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

akelad commented 5 years ago

@erohmensing what's the status here?

erohmensing commented 5 years ago

Looks like the issue might be with .format() which we use... in all of our logging: https://stackoverflow.com/questions/27150858/print-succeeds-but-logging-module-throws-exception not sure how to handle it in this case

erohmensing commented 5 years ago

Update, intent name isn't the issue, in an ascii codec environment I got the following with no error: 

2019-06-20 12:57:40 DEBUG    rasa.core.processor  - Received user message 'hi' with intent '{'name': 'greet\U0001f919', 'confidence': 0.9477102160453796}' and entities '[]'

I think we can close this?

akelad commented 5 years ago

closing then