I've been trying to use batch testing to test my luis app and have been experiencing an annoying bug. Basically the LUIS app page will become unresponsive while the batch testing window is open.
The most similar issue I've seen can be found here: LUIS web interface crashed after import JSON file for Batch Testing or Import App, with no answer yet.
My problem is also slightly different by the looks of it.
Experimenting has yielded the following results:
I can upload, test and view the results of 1 batch successfully sometimes. Sometimes the page will become unresponsive while I am looking at the results.
If I have successfully viewed the batch, but then close the batch testing window without deleting the batch, the next time I open the window the whole site will become unresponsive.
Recently opening the "Inspect" tab on the single utterance testing window has also begun making the page unresponsive.
I can submit images if needed, but the pages seem more or less the same after the bug has occurred, they simply stop working. Pressing buttons does nothing and I need to refresh the page if I want to get back to the bot's Dashboard/Build/Publish/Settings page.
The app has 18 intents, 12 entities, and a couple hundred utterances. I have tested it on a collaborator account and the bugs seems to occur there too. Not sure what other info might be relevant.
If anyone has experienced similar issues and can help I'd appreciate it. Being able to use the built in Batch Testing feature would be very useful.
Related
I'm currently on a team developing a Slack bot, we've begun the classic console.log debugging strategy and our log output is already getting extremely bloated. A team lead mentioned breakpoints and I decided it would probably be a good idea to start using them but there is a problem:
Slack bots are sometimes responding to requests in a time-sensitive manner. For instance, when opening a modal you only have 3 seconds following a user action to open the modal, clearly any breakpoint that halts execution before the modal is opened would cause problems.
Thinking about it, it seems like something that /should/ be possible. When reaching the breakpoint simply take the stack/vars that would be displayed and store/display them without halting execution. Unfortunately, 90% of the time I think "this should exist", it doesn't.
Well, I guess I could just google it huh?
IntelliJ - Tracepoint
VSCode - Logpoint
I've updated the icon for my bot in the Azure portal about 35 hours ago, but it's still showing the old one for new messages sent from the bot. Surely it should have changed by now? Is there any issue with this currently?
It's correct in the Azure portal in the "Test in Web Chat", but Teams is still showing the old icon, even for new messages.
Update:
It's been a few days now, and the image finally changed, but now it's totally corrupted. Is there a way to see what's wrong with my PNG? Is there an issue with the bot framework/Teams of some sort? See images below:
Error:
Original Icon (I don't know if SO changes the file in any way, but presumably not)
Update: I've now modified my bot in the Azure portal to use the exact same icon as another bot which is working fine, and it's still broken, so I'm thinking there is an issue with the bot framework/Teams in some way at the moment.
What I've encountered from experience is that when updating the bot's info in "Bot App Registration" such as icon and display name.
You can either wait a couple days and see if it fixes itself.
I've consistently been able to get it to update sooner by logging in and out of Teams as well as closing it.
I have a feeling that it's related to the cache since Teams is built with Electron. Some other post mentioned this and there's no "official" surefire way to do this. Playing with the manifest also does not seem to affect it to update sooner.
TL;DR
Log in and out of Teams, close it. If using web version, clear the cache. Log back in.
Good luck!
Try reinstalling the application on Teams, sometimes it takes time.
I have a Mac desktop application developed using Xamarin.Mac and XCode. The application is loading views that should have a considerable amount of content as blank/white screens for a select few end users. While I've not been able to reproduce the issue locally and it doesn't appear to be impacting many people, it does happen consistently for a handful of users(6 out of over 4,000 at the moment). The app works just fine for the vast majority and uses a main window controller that sets the content view as needed by calling the applicable ViewController. When the views in question are loaded for the given users, it renders as a blank white area.
I did notice however that at least some of the objects in the views are actually there, just not visible. For instance, one view has buttons that are still "there" as you can click on them if you know where they are supposed to be positioned(and they also fire correctly) but they are not actually visible as the area is all white with no visible content. It's as if everything is loading properly but the UI just isn't cooperating in displaying objects that are actually there. The closest thing I could find was this Diagnosing run loop issue (partially frozen UI) in Cocoa application
However I'm not sure it's the same problem and there was no resolution for that either. Has anyone else ever encountered something like this?
Ok, got some new info. After doing a remote session with a user we had no luck with the hardware and the console didn't provide much insight, however we did stumble across a workaround that fixes the issue and may give some clues as to the real problem.
When the application is initially installed, we prompt the user to ask if they want it moved to the default Applications directory. They do not have to move it as it will work the same from pretty much anywhere but we do this for convenience. For the users having this problem, we noticed that they all had the app installed in the Applications folder. By sheer luck, one user accidentally chose to not move the app after reinstalling it per our support team. When the app was installed in his default Downloads directory, the problem vanished and the app worked as expected.
After testing various other directory locations(Downloads, Documents, etc.) we found that the issue only seemed to exist if the app was installed in the Applications directory. Furthermore, if the app was installed in the Applications directory, we could simply move it or copy/paste it to another directory outside Applications and when launching it from that new location the issue was resolved.
Seems like there is something specific to the default Applications directory that is causing this to happen(as odd as that sounds). Keep in mind that even when the app is installed in the Applications directory, this issue only happens to 7 people out of over 4,000.
Any ideas as to what might be special about that directory that could explain what we're seeing?
I have a cocoa application where each document is basically a webview. It works very nicely, but I noticed that when I have a javascript routine running, the interface locks up. I downloaded the tutorial code from the apple docs, and in there, it works fine ! The only major difference I can still spot, is that the tutorial uses a single window and is not document-based.
so I am assuming that this is the culprit. However, I am totally lost in how to solve this
i've uploaded a screenshot here : (removed because i don't have 10 rep yet so i can only post one link) and you can see that I have two xib files : one for the app and one for the doc...
can anyone hint me how to handle this ?
EDIT : after crunching my brain for a whole night, i came to the conclusion that even on single window it doesn't work... I managed to make a very small test experiment here : http://noglangengelukkig.be/ex.zip
opening, compiling and running it will work fine, but as long as the network is stabilizing (= the nodes are still finding position), you can't click.
the page that it is showing is this one : http://www.beergraph.xyz so you can see that it works perfectly in safari !
i found it... i'm an idiot... the reason things locked up was NOT webkit : it was the fact that the javascript code could not figure out which browser was running it, and thus assumed that setTimeOut() didn't exist and fell back to blocked-timing
I'm getting logged out of all Google services a set period after opening the browser or logging in, it's about 20 minutes, maybe less. Occasionally the log in page will automatically redirect to a "clear cache and cookies" help page, however following the instructions on this page changes nothing and a short time later it logs me out again. This is particularly annoying when writing a response to a review on the Google Play Developer Console, because as soon as it detects being logged out it greys the text box so that it's not possible to copy and paste the message and it is not saved as a draft, it has to be written again. It's important to note this happens regardless of the browser being used and regardless of whether or not you are logged in on multiple devices. This is something Google really need to fix. Has anyone else suffered these problems?
It appears I've found a solution, as an Android app developer I always have a bunch of tabs open such as Google Play Developer Console for reviews and statistics and Google Wallet for financial reports. It turns out the problem is related to Google Wallet because if I close this tab, it won't log me out of all Google services. It appears this is a bug with the Google Wallet service. So to clarify this is a bug with Google Wallet, so if you're experiencing this problem like me, always close this tab after viewing the reports (the one launched from the Play console under financial reports).