-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Training from wit.ai data causes exception in extractor.py #7676
Comments
cc @RasaHQ/enable-squad |
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. |
Facing the same issue. Please help. @sara-tagger @wochinge |
@roots-ai Would you mind creating a PR with the necessary fixes? Unfortunately the team is currently very busy with 3.0 so I don't think we can tackle this one soon ourselves |
|
It seems like we are missing to set the |
Any expected timeline for when it be possible for the team to fix this? I installed RASA from the source and made the above changes and now it gives this new error
|
@roots-ai Sorry, as I said in my previous comment it's currently very busy and I can't provide a reliable timeline |
@wochinge Would be good to put this as a disclaimer on the |
Since you've asked so nicely I've created a PR with the necessary changes: #9864 |
Cutting a release today/tomorrow for this |
Rasa version: 2.2.2
Rasa SDK version (if used & relevant): 2.2.0
Rasa X version (if used & relevant): None
Python version: 3.8.5
Operating system (windows, osx, ...): WSL (Linux-4.4.0-19041-Microsoft-x86_64-with-glibc2.29)
Issue:
Following the instructions to convert my wit.ai data to Rasa training data results in a Python exception. I followed these instructions: https://rasa.com/docs/rasa/migrate-from/facebook-wit-ai-to-rasa/
My
utterances-1.json
file is present in thedata/
folder as noted in the migration instructions.Error (including full traceback):
Command or request that led to error:
Content of configuration file (config.yml) (if relevant): N/A
Content of domain file (domain.yml) (if relevant): N/A
The text was updated successfully, but these errors were encountered: