I've been playing with WitAI recently to see what it can do, and I had built a user flow of about 5/6 questions, with a couple of Yes/No/I don't know branches etc. I've set up a couple of "bot executes" options with the hope in the future that I will write some function on my side to do data processing etc.
But on every save now, I see a red light on the left side saying "Your app may fail to handle this story properly".
I've rebuilt a use flow with no bot executes, and no branches, and I've trained up the bot on each sentence to expect, but I still see this. I'm really confused, as there are no fields highlighted red to suggest that the bot doesn't understand that line. Can anyone help out here?
Related
I have a React program/game that I need to run at the same time for every person viewing. Every time I load it locally, it produces a different output and I basically need it to be run server side one singular time, but I have no idea where to start. I've tried googling stuff but I'm not wordsmithing my searches correctly because I can't find anything relevant. Anything helps, thank you! (If this doesn't make sense, picture a "premier" of something special, where it happens at a set time for everybody)
I'm having trouble avoiding the FallbackIntent. I'm writing a skill that labels different days Red Days or Blue Days. Using the dev console Utterance Profile I keep getting the fallback intent when I ask "is today a red day". I have a specific sample of that question in my interaction model so I don't understand why my intent is not getting identified. Does anyone have a suggestion?
specyfying the skill name does not help
Saving is not enough, you missed the "build model" button so the utterance profiler will be able to evaluate your utterances.
After building, you can see it work properly.
Also, I recommend you to keep AMAZON.FallbackIntent in case your user is saying something not defined in your Interaction model. You might want to catch that.
I hope it's the right place to ask such question. I have a live react app which still runs in development mode since it requires frequent updates, and it seems that for a few users the website doesn't function properly while for the others it works perfectly.
For example, for a few users there is a button that just doesn't respond, although I created some code to log to the console that the button was pressed, and it does also for those users, but then the rest of the code just doesn't run.
For other users, there is some text that loaded from mongodb database, and for those users it reverses some of the words in a random fashion.
I'm really lost here and don't even know where to begin, since for me and most of the users everything is working fine.
Do you think it could be because the app still runs in development mode?
Recently I noticed that a few users received the message
the development server has disconnected. refresh the page if necessary.
I researched this and was suggested that I should upgrade my react-scripts. I did, and the problem vanished, but the other problems still persist.
I understand that it's like shooting in the dark and it's hard to give advices without knowing more information, but maybe you could point me in the right direction?
Thank you very much in advance
EDIT : (rewrite)
So, I'm doing a mini-games bot for my discord server. I have already done a bot with multiples features and it was organize like that :
- My main was handling my events. I was checking where my event was called and according to the channel, I will run my corresponding file.js.
- I have my main folder, with inside, one folder with my commands, one with my "handler" (like members counting, and other autonomous things), and the last one with my images.
Do you think it's correct, bad, and what can I improve ?
Can you send me your idea or your point on vue on that.
I try to make my code better each time I code, and organization is one of the thing I want to improve.
I hope it's a much more understandable.
Please read the handy DiscordJS Guide that covers this subject and maybe put a little more effort into your research next time: https://discordjs.guide/command-handling/#individual-command-files
I am working on an application on Google App Engine. Roughly this is what I do:
The user screen is split into 2 parts (actually 3, but lets leave that out for now). The left part (this takes upto 75% of the screen) has a document with some words highlighted. When one of these highlighted words are clicked the right part displays various meanings of it, example usage etc. The way this works is clicking the word send an XML HTTP Request to the server, where the sample usage(s)/meaning(s) are retrieved from the datastore. This data is returned and displayed.
My problem:
After I click on a few words consecutively, the application seems to "hang" - say, I click on 5 words in quick succession, clicking on the 6th word (or any word after that) doesn't replace the info regarding the 5th word on my right panel.
Since some data store columns (at least single valued properties) are indexed by default I'm guessing retrieval is not the bottleneck here. It is probably the requests.
Is such an issue known with the GAE? Any workarounds possible?
Kind of in a soup with this - the application was supposed to go live today. Urgent help required!
Thanks! :)
You're probably being limited to two simultaneous requests by your browser - not by appengine. If you click on a third link before the first two have had a chance to return, make sure your app can deal with requests returning for links that should no longer be displayed.
If you were hitting a limit on appengine, you'd see exceptions in your server logs. If you're not seeing those exceptions, it's probably a client-side issue.
Sorry for the late ack (for some reason I received a notification for the responses a day late, by which we had managed to fix a few things). It does look like the problem was at the data end - our code was doing some inserts, and it turns out you can't do too many of them quickly - the logs reported a transaction time-out error. The reason we couldn't spot it earlier in the logs was we were writing simply too much info out and this was buried in somewhere.
The clicks on the user-side were pulling data from this table.
Unfortunately, the GAE simulator doesn't simulate any timeout error - so even though we had tested with comparable volumes of data before deployment this error never happened during development.
Thanks again for your responses!
And yet again, I apologize for responding late.