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
slot names cannot accept numerals #278
Comments
Goodmorning Pico, this morning I started a new Rhino context and imported the .yml that caused the error and guess what: there is no error when I press the mic button.... So that seems to work again. What remains is that I cannot use digits anymore. |
happy that this is resolved. @ErisMik can you please look into why numerics are not accepted? I thought we expanded the set of acceptable chars. |
The Rhino editor has been updated to allow for using numerals in |
Goodmorning Erik, apologies for not replying sooner. I was able to try and use digits this morning and it all looks good now. I reckon you also would like to know if the problem is solved ;-). Thanks! |
@JPCDekker Could you please export the context that results in that error as YAML and post it here? |
Hi Eric, I coded a new context and tested it yesterday. But this morning I got the error again. It seems the error appears when my laptop has gone to hybernate and started back up again (though some older contexts still work properly). So it might be a browser thing (I am using Firefox) but I am no expert. Logging out of the Pico account, refreshing the page and logging in doesn't work. Please find the exported new set attached. |
Hi there,
I have been using the Picovoice console for some time now and I really like it. But since two days I get an error when I want to rebuild new context from the console. The context was created entirely in the console (I didn't change the .yaml file and uploaded it to the console). After pressing the microphone icon, the context is saved and rebuilt but then the process stops in the “WA” phase and the message “Error retrieving context” appears.
I am using Firefox but got the same with Chrome.
Also I found that I cannot use a digit anymore to indicate different slot phrases like room1 and room2 in new intents while in already existing intents the digits still work. Could this be related to the error mentioned above?
Cheers! Jeroen.
The text was updated successfully, but these errors were encountered: