You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Try saying "stock market".
2. The system crashes.
3.
What is the expected output? What do you see instead?
If there was no pattern matched to the input, it used to just show up blank,
which is what I want. Now, however, it crashes with the error listed below.
What version of the product are you using? On what operating system?
I'm using my own compilation (attached) running using AssistantExtensions (via
Cydia) on my (jailbroken) iPhone 4S.
Please provide any additional information below.
Receive this error every time an unmatched pattern is received:
"My brain just exploded. Error 13: No match found. There should be at least a
pickup line (<pattern>*<that>*<topic>*)"
Also, I'm trying to run this on my iPhone. I'm working on a project for my
Markup Languages class in college, and was trying to whittle away any and all
unnecessary files. I'm not sure if you'll be able to figure out what's
happening without using the iPhone, but this is driving my nuts, so any help is
appreciated.
Original issue reported on code.google.com by joecaval...@gmail.com on 24 Feb 2012 at 8:55
I apologize if this is the absolute wrong place to post this, but I am unable
to receive responses from anyone in the AIML community, including Dr. Wallace.
Original comment by joecaval...@gmail.com on 24 Feb 2012 at 9:00
Sounds more like an iPhone issue or something you've added because there are
replies to "stock market" and plenty of pick up lines when there is no pattern
match.
Try emailing your question to info@pandorabots.com or posting at
http://knytetrypper.proboards.com/index.cgi?board=apps (chatbot apps section).
You can also try these:
http://forum.alicebot.org
http://www.chatbots.org/ai_zone/
Original comment by zogb...@yahoo.com on 25 Feb 2012 at 11:15
Original issue reported on code.google.com by
joecaval...@gmail.com
on 24 Feb 2012 at 8:55Attachments:
The text was updated successfully, but these errors were encountered: