Closed habeeb-umo closed 6 years ago
Thanks for taking the time to file a report. You haven't given me the steps to reproduce this error but I assume it occurs during requests for updates.
As I am not able to replicate the issue, can you tell me in detail what steps you have taken following installing the package.
Alongside this, are you aware of any unusual conditions of your network which may be interfering with an API request (proxy, vpn, .etc)?
Seems to happen every time this morning, and Atom v1.25.0 has just come out.
I get the same stack trace, and this happens every time I start Atom. I've manually upgraded to 1.25.0 and still see the error on starting Atom.
Looking at the code and the url it calls, I can curl https://api.github.com/repos/atom/atom/releases, which returns...
{
"message": "API rate limit exceeded for {AN IP THAT LEADS BACK TO THE COMPANY I WORK FOR}. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
"documentation_url": "https://developer.github.com/v3/#rate-limiting"
}
So if anyone else sees this issue, maybe curl that URL. For the code, maybe gracefully fail, or surface the error message in some way? Definitely want to handle the response body not being an array though :)
@andyedwardsdfdl Thanks for the additional information.
After some investigation, it looks as though this is due to the API rate limit for your IP being exceeded.
I am working on providing cleaner output - expect a fix within the next week or so.
Atom: 1.23.3 x64 Electron: 1.6.15 OS: Ubuntu 16.04.2 Thrown From: atom-updater-linux package 1.0.6
Stack Trace
Uncaught TypeError: response.some is not a function
Commands
Non-Core Packages