I made this URL public a few years ago as a way to retrieve data. It was working yesterday. Today my site is crashing as it relies on this data, but google is now returning a 500 error if I try to retrieve it programmatically (through axios).
https://spreadsheets.google.com/feeds/list/1DLAVN3q758sPohCFeZlVSVRZKXzEser1SIsQnH2mvrw/ogwtdyp/public/basic?hl=en_US&alt=json
I have also created a code sandobox with react to demonstrate: https://codesandbox.io/embed/xjmy9vl2z4
However, I am still able to view the response in the browser if I am logged in.
Did google recently change their API so that it is no longer possible to retrieve data this way? Is there a way to configure my axios request in such a way to continue retrieving this data?
UPDATE:
Issue is being tracked here: https://issuetracker.google.com/issues/131613284
According to the support team: "The engineering team believes they have located the source of the problem and are rolling back to a previous build in order to resolve issue. Please stand by."
https://issuetracker.google.com/issues/131613284#comment109
UPDATE:
It seems like the issue has been resolved by rolling back to a previous build. I am no longer experiencing these issues. The link above, and the code sandbox example are both functioning. Reading the forum, it seems like others are also no longer experiencing issues. If you are still experiencing issues, I would encourage opening another (perhaps more specific) post or issue.
Related
I'm trying to write a simple KB-CVE matching program, and I want to use data provided by Microsoft Security Response Center. Since I'm new, I searched a little and learned to work with developer API.
Problem is after I learned to work with it, I figured it has been returning 503 Error code for quite a long time (link to open issue in GitHub repo).
Now the only way I know, is downloading data from Security Update Guide
manually and then writing a simple program to search data and find the result. which is really not what I want. I'm looking for an automatic way.
The goal is to take KB number, and find all CVEs related to it. Now in order to this I have to manually download my dataset whereas with API I was able to just enter the URL for a specific KB and find all data related to it.
So basically I'm looking for a some URL which is capable of getting all data related to a specific KB now that API server is unavailable.
I'm developing an app that interacts with Mendeley API. Retrieving and updating documents work fine, but I fail to retrieve the ID list of deleted documents, as described in API Reference. Instead, I get 404-error, with the message:
{
"message": "No service found for your request"
}
Looks like this API is not implemented, even though listed in the Reference. Emailing Mendeley API team is of no help (I wrote to them about a different issue 3 months ago, they just don't answer). Anyone worked with that?
Ok, it seems they just don't update properly the info for developers. From the "Explore APIs" section on their site I have found that I should use "deleted_since" URL-parameter, rather than "deleted_documents", as stated in the "API Reference" section on the same site. The "deleted_since" works as expected.
As this thread has opened four years ago, and I was looking for a possible answer to this exact error when using the Mendeley desktop's latest release yesterday, I think it's appropriate to mention such error's occurring to the users. I finally had to reinstall after the total removal of the program from my SSD after importing a lot of references from another reference manager's RIS file. I suppose it has something to do with the server and the desktop app not being completely synced.
It is worth reinstalling if you've had the same problem and have not lost all your library's online material.
Mendeley 1.19.8 on win 10 C64 19044.1706.
I found a lot of posts about this issue, but none is like mine.
I have a website that subscribes to IG real-time updates. Since some time ago trying to subscribe to new notifications returns the above error. Seems like IG can't reach the callback_url.
Interesting findings while troubleshooting:
I tried to manually (directly) access the callback_url and it works flawlessly.
When I run the site on my local machine and make sure the callback_url is to my server + the verify_token is a valid one then it all works as it should! IG reaches the callback_url.
I used the apigee console to make the subscription request and there it sometimes works.. Meaning - I craft the request to IG API and click Send. If it fails then I click again (I don't change parameters) and then it works..
Web server logs are in line with the results I get (when it complains it can't reach then there's no log of a request).
Does anyone have any tip or suggestion how to fix this?
Thanks!
While chasing my own tail for a solution I also contacted IG support. I described the issue using same description as above.
After 2 weeks suddenly everything started working again. Magic! Suddenly no errors at all! Needless to say nothing has changed on my end (hardware / network / code).
I didn't receive any response from their support, but considering that a previous email to them a few months ago took about 2 weeks to answer then I am quite sure some support guy simply fixed the issue on their side and didn't even bother to let me know what was going on.
This could be related to the fact that they killed most of their real time notifications API.
Anyway, leaving this here so that if anyone encounters a similar issue then just know you may need to email IG support.
I had a really frustrating issue recently with Tweetdeck, a tool to manage multiple twitter accounts. Since we get feedback and support questions on Twitter accounts with our projects, it is MUCH easier to see all the information in one place. That said, I had a recent issue and couldn't find ANY help online. I was able to find and test a workaround though, and have decided since it helped me I should post it here.
First, let me explain the exact issue, so you can see if my solution might work for you (YES, I already have the answer and posted it below)
I know my Tweetdeck was working previously (as I had multiple accounts). Since some of the projects were going away, and new ones were starting, I removed the existing ones and started trying to add the new ones.
The twitter page would come up asking to authenticate, then after typing in the information, I would get a generic "You have been logged into Tweetdeck, please return to the application" in the new window, but when closing it, I would not be logged in on Tweetdeck with the other account (only the original one)
I tried NUMEROUS steps to fix this including some of the following (NONE of these steps worked):
Tried different computers (with different Operating Systems). These included Windows 7 and Linux (Ubuntu 10.04) and more than one browser (Google Chrome, Firefox, etc). I also tried clearing cache, cookies, history, etc.
NOTE: I also tried to contact both Tweetdeck and Twitter support, neither of which have ever responded to any question I have ever had in years.
So the initial question was... "How do I get Tweetdeck to authenticate with other accounts successfully" with the error "You have been logged into Tweetdeck, please return to the application", but the new accounts do not actually authenticate and I cannot use them in Tweetdeck.
After extensive attempts to find a way to make my Tweetdeck work once again, I found a workaround that has worked great for me. I am not sure exactly why this works, but I have a feeling it has to do with the difference between the authentication method of just Tweetdeck online vs. the Google Chrome App.
On a whim, I decided to install the actual Google Chrome App plugin (as I was running out of options). Then, when using the app, it succeeded with no problems.
While I have posted an answer that works for me here, I would appreciate any comments that might give more real information (not guesses) on why this happened. If there is something else I can try so that I am not limited to the Google Chrome App if I want to add new accounts, I would also be happy to try those possible solutions. Please make sure to read my question which covers what I have already done.
NOTE: Since I have a working workaround, if your solution will take substantial effort, I will probably not try it .
we are developing an extension, hosted in the Google chrome web store.recently - we've got complaints from our users that sometime they get a notification window saying "the extension crashed, click here to reload".
after a short research we found out that this is happening only when we upload a new version to the Chrome Web Store.
we started to look it up online and found no documentation what so ever for this, so we started to check for it ourselves.
we tried to see what exactly can cause this problem and if we can identify a distinctive cause.
our tries included updating only the manifest.json file, a css file, a js file or not changing nothing at all but the version number, and on each change we've uploaded a new version and update it in about 10 different machines.
the results were the same, when on each update we made, it caused the extension to crash on just a few of the machines, while updating perfectly fine on the others. each time different machines acted differently.
then, we thought it might be related to the fact we have a timer working in the background page, and it might be happening just at the time it is working.
so we tried to raise the timer's frequency (from 5 seconds to 100 millisecond), and it still acted the same, crashing on only 3 out of the 10 machines.
we ran out of ideas now, and it really causing a problem in terms of user experience to our extension's users.
did someone had this problem, or came across any extension crashes on version update?
is it a known bug in chrome's extension engine or are we doing something wrong?
I am having the same problem and I think I found the cause. Do you by chance, override the new tab page?
I am able to reproduce the problem 100% of the time and when I remove the new tab override from the manifest, the problem goes away.
I opened an issue: Issue 104401