I am observing some really strange behavior.
Sometimes the following URL works, sometimes it just says "Connect Failure" No definitions found.
Is there a timeout? It might work 1 out of 10-15 times, I have tried waiting for 10minutes but it just keeps saying the same. Stability issues? Something I'm doing wrong? What's happening?
http://query.yahooapis.com/v1/public/yql?q=select%20Name,Symbol,LastTradePriceOnly,Volume,Change%20from%20yahoo.finance.quotes%20where%20symbol%20in%20(%22AAPL%22%2C%22GOOGL%22)&format=json&diagnostics=true&env=store://datatables.org/alltableswithkeys
Related
I only have 15-20 messages in my inbox for June 20. But when I run a search query for that day
https://graph.microsoft.com/v1.0/me/mailFolders/inbox/messages?$search=" received = 2019/06/20"&$select=from,id&$top=1000
I am seeing that the results are repeating, meaning the same message id keeps circling back (think its an infinitely) and the results take several seconds to return.
I am even able to reproduce that with Graph explorer. It doesn't seem to happen for other days in my inbox. I think I have come across some bug in the system but unclear what exactly it is.
Anyone know what it is?
This issue is now fixed. Can you pls try again?
I have got an error issue.
Every time I say OK Google it answers with:
Something went wrong, try again in a few seconds
or
There was a glitch
Now my Raspberry assist does not do anything anymore.....
I searched the web and saw there was an issue involving this some time ago after an update of Philips Hue. But I do not have any Hue's around. So that is not it.
This happened after I added some recipes on IFTTT that connected to Google Assistant.
Anybody else getting this error?
Luc
Self fulfilling prophecy.
After a day without any action from my side it suddenly started working again. Maybe IFTTT had to do some cleanup overnight and that ended a loop. I really do not know what caused it to start working again.
So the solution to this problem (for now) seems to just have some patience.
Luc
The operation couldn’t be completed. An internal error occurred in the Places API library. If you believe this error represents a bug, please file a report using the instructions on our community and support page (https://developers.google.com/places/support).
I'm using the Current Place api and I'm getting this error the entire day today. It worked fine until now but today it started trowing that error every time.
I thought it could be because of the limits, but I've raised the limit by enabling billing and I also saw in google developers console that I had 50 requests for the last day and 500 for the entire month. Default limit is 1000 requests per day or 150k per day if you've enabled billing. So it seems like this is not the reason.
Any ideas what could cause this problem?
Judging on other people's comments and this answer it seems like this was a temporary issue on Google's end. Everything started working on it's own.
I am getting intermittent 500 errors when hitting the YouTube ContentID/partner API. At times, this is the response:
{"errors":[{"domain":"youtubePartner","reason":"internalError","message":"An internal error has occurred."}],"code":500,"message":"An internal error has occurred."}
At other times, this is the response
{"code":500,"message":null}
And at other times, the request succeeds.
This is happening most often when inserting a claim, next most often when setting ownership and, less often but still happening, when creating an asset and when setting advertising options.
Is there any alternative to adding retry logic?
There are most likely transient errors, you can just implement an exponential backoff retry policy and that would do best for now.
On the other hand, issue should've been fixed by now.
We're writing an application which uses our http api, and occasionally it will encounter errors, failed connections, timeouts, etc.
We'd like to, at least in beta, be able to capture these incidents, and forward them to ourselves somehow. Since obviously many of these issues could be due to the actual connection being down, this would need to queue these incidents and send them when a connection is available.
I tried googling for an answer for this but to no avail, came across a bunch of solutions which catch exceptions, but not just random "incidents" (could really just be a string we log somewhere, we'd just include all the details in it).
Short of writing my own coredata (or something) backed queue, I'm at a loss at what a solution for this could be.
Does anyone know of any libs/services which could help with this?
You might want to look into Testflight, or less general purpose, Parse. Not quite sure, but maybe HockeyKit offers a solution for this, too.
You can take a look at Bugfender, it's a product we have built to solve this problem. We have found that while developing an app there are a lot of issues that are not crashes, so we decided to make our own product to help us on this.
It's easy to integrate and you can get the devices logs. Our service works offline and online, we have spent a lot of time to make it reliable and easy to use.
Compared to other products, you don't need any crash to get the logs, you choose when you want them.