Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Totally broken #25723

Open
mjrodgers opened this issue Nov 29, 2022 · 4 comments
Open

Totally broken #25723

mjrodgers opened this issue Nov 29, 2022 · 4 comments

Comments

@mjrodgers
Copy link

mjrodgers commented Nov 29, 2022

How frustrating for the last "sunsetting" update to the program to actually break all of the functionality.

Since 1.63 update on macOS (even with 1.63.1)

  • I get a big giant warning that Atom "Failed to activate the ide-python package" due to "callGetFileName is not a function"
  • There are several deprecation warnings, including from atom core.
    This is in addition to the package downloading/uploading which has already been broken for several months.

I know no one will look at this or care, but the way in which this project was sabotaged and killed by Microsoft is really shameful.

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Dec 1, 2022

Speaking as someone somewhat familiar with this repo/code:

Some incompatibility with a few ide-* packages was a known issue from the Electron 11 upgrade.

The package upload/download issue is because the website atom.io has been flaky, and that website/server hosts the package registry and API for Atom packages.

If it were me, I would be more conservative and base the final release on Electron 9, since Electron 11 only made it to Atom Beta and didn't get super wide testing, had the few known issues such as with the ide-* packages, and just because putting out a "sunset" message should likely be done as the smallest change possible. I would have suggested this be done against the 1.60-releases branch (the branch from the previous stable Atom release).

I can see how easy it would be to just publish from master and not flag the Electron 11 bump as a problem for some users. This repo and its tooling are hard to work with. It's a huge code-base to be familiar with if you're not actively knee-deep in it on the daily. (And it'd be a bit awkward to leave out some large amount of effort and PRs which various people have contributed to master branch after 1.60.0 Stable, without including them in the final Atom Stable.) I do not believe it was malicious or a deliberate "sabotage" FWIW, I think it was just an oversight and/or not being conservative around the Electron 11 bump promoting to Stable from master branch and Beta.

If you get the point of the sunset message (I think we all do), I guess a workaround could be to disable automatic updates and use the old 1.60.x stable version. Particularly if you need those ide packages.

@nreef12
Copy link

nreef12 commented Dec 7, 2022

I recommend switching to Photon, it's a community fork of Atom which fixes a lot of things and keeps Atom going

@LouieTian0209
Copy link

I recommend switching to Photon, it's a community fork of Atom which fixes a lot of things and keeps Atom going

I'm assuming you are talking about Pulsar?

@nreef12
Copy link

nreef12 commented Dec 15, 2022

I recommend switching to Photon, it's a community fork of Atom which fixes a lot of things and keeps Atom going

I'm assuming you are talking about Pulsar?

Yes lmao :P

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants