search

atom-community / atom

:atom: Community build of the hackable text editor
https://atom-community.github.io/
MIT License
745 stars 30 forks source link

cant install/search/update packages (api down) #459

Open shellscape opened 2 years ago

shellscape commented 2 years ago

With atom.io/api being down (returning Application Error for all requests) how is everyone who uses this project working around that error when installing/searching/updating packages?

confused-Techie commented 2 years ago

The long term workaround that I'm aware of, could be to help contribute to a community made replacement.

This would be hopefully an exact mirror of the current API to use in the future. As of now its really just retry, since the server doesn't always return an error, just about 90% of the time it does.

ghost commented 2 years ago

I could install atom-ide-base directly from the original Atom's settings, so I don't know if this is true for all.

I'm still able to access atom.io, so I guess this is not for everyone

@confused-Techie 's 90% claim is not for everyone, I even checked my browser console logs for errors, only failed to load resource(blocked by client errors), and a spelling uncaught reference error for "twttr"

confused-Techie commented 2 years ago

@stech11845 Sorry if I made that seem like a concrete fact, yeah 90% won't always be true. Just what it seems like in my personal experience, when querying the API to test development and parity with my backend recreation, seems about 90% of the time it fails. But might just be my location, or luck.

Additionally in the meantime, you could look at installing the packages directly from GitHub if theres only one you need, or adding the link to an NPM version.

Additionally theres this pull request on the Pulsar Fork of Atom, that aims to temporarily solve this problem for some packages while in development if that helps.

shellscape commented 2 years ago

I'm speaking with a lead devrel via Twitter and there are some folks working on a fix. Latest update was that there were permissions issues.

ghost commented 2 years ago

@stech11845 Sorry if I made that seem like a concrete fact, yeah 90% won't always be true. Just what it seems like in my personal experience, when querying the API to test development and parity with my backend recreation, seems about 90% of the time it fails. But might just be my location, or luck.

Additionally in the meantime, you could look at installing the packages directly from GitHub if theres only one you need, or adding the link to an NPM version.

Additionally theres this pull request on the Pulsar Fork of Atom, that aims to temporarily solve this problem for some packages while in development if that helps.

I guess, how long the distance between where the server is hosted and where you live.

shellscape commented 2 years ago

true, it's prob connected to a T1 or DSL line. 🤣

ghost commented 2 years ago

true, it's prob connected to a T1 or DSL line. 🤣

DSL line? Not even for the modern days.😅