-
Notifications
You must be signed in to change notification settings - Fork 161
Incompatible with Atom 1.39.0 - Discussion on Current state of affairs #707
Comments
duplicate of #700 |
I get a little bug icon on the bottom of the window. If you click that, you get some info about incompatibility. YOu also get the option to rebuild the package. Clicking that option seems to work. After restarting atom, the package works. |
@pdxwolfy Thanks for providing that information, though can you provide a screenshot so as to help those of us who need to see exactly what they should be looking for? Also node-gyp has been reported to fail with any other python version higher than 2.7.0 most people use higher or current versions of python. Did you install anything specific to that? If so please provide this information if possible with step-by-step instructions so that the less technical of users can follow. Thanks in advance for your attention to this matter. |
Hi the-j0k3r, Yes, I have both python2 and python3 installed via homebrew, and Unfortunately, I can't post a screen shot now since it was only present before I rebuilt the package. When I started Atom before that, there was a little bug icon down on the right side of the status line. I clicked that icon to see what it was about, and that's when I got the message about incompatibility. There was a clickable item on the screen that said "Rebuild packages", and I did. When it finished, it restarted Atom, and the complaint about incompatibility was gone, and the terminal was once again working. I'm sorry that I can't provide more info than that. Oh, the tab that had the messages about incompatibility was labeled "Incompatible Packages"; you can get there with. You can open it from the command pallette |
Installed Atom 1.39 then tried to install platformio-ide-terminal @pdxwolfy sadly I see no such icon, but I will retry. Also, homebrew is macOS, Im on Windows 10 pro 1809 Atom sadly doesnt seem to be consistent across OS's Its similar but not exactly the same What I did
Did not see any icon and failure as above. I will try installing older Atom 1.38.2 and platformio-ide-terminal 2.9.1 and then letting Atom upgrade. |
@the-j0k3r try the following
|
OK heres how I got to see the bug ICON
Result failure same as above 3rd try, what @UziTech suggested.
Both Atom 1.38.2 + upgrade or @UziTech instructions result in |
Tried also with nodejs 8.9.3 but node-gyp is severely outdated in Atom more specifically apm, node-pty-prebuilt has lost its maintainer/developer to Microsoft. No idea, its extremely frustrating also becaise all devs are bailing Atom and related plugins/dependencies EDIT: @UziTech Due to the sheer number of direct project dependencies and the indirect dependencies ( dependencies of the dependencies) its impossible to satisfy your suggestion of taking responsibility for their failures (hence wontfix label will be staying whether this is ideal or not while I take care of the issue tracker here. I admit, as a issue tracker contributor for this project and because of #543 and the lack of developer contributors for this project have forced me to adopt the strict constrictions regarding such dependencies. It would be insane amount of reports that no one looks at from a developer standpoint in 95% of cases (because only 5% of those cases had developers pushing contributions to address them in most recent times after the main developer called it quits). Also issue reports quality are extremely poor in this project as most people ignore the issue templates which were added to at least provide actionable information in order to find fixes/workarounds to that do provide full information, I have endeavored to find/post/repost workarounds as they are found. As of Atom 1.39.0 and OS depending (for successful) node-gyp rebuilds, ALL terminals that depend on node-pty-prebuilt are dead (the dev/maintainer now works for Microsoft and responds to no emails/contact attempts). We need alternatives (for terminals and dependencies and developers to implement them) and other than VScode. Atom devs that used such terminals will either do something about it or ignore the issue unless someone capable comes along that is able to address these issues. Im trying not to sound/come across as caustic or as a troll if any of this is offensive, I will pre-emptively apologise as its not my intention. |
I was able to rebuild the package on Windows 10 x64 1903 and now it's working in Atom 1.39.0 x64.
|
Solution #3Here is a solution that will almost certainly work for all OS/platforms that have prebuilt modules in that repo. See https://github.com/pfitzseb/node-pty-prebuilt/releases choose a platform that matches your OS, I recommend you stick to stable builds only around 0.8.1 at this time. scan the hell out of these with antivirus or audit the code. Close Atom, Download the asset for your platform, replace the contents of Atom/packages/platformio-ide-terminal/node-pty-prebuilt etc etc with the downloaded bits from there. Open Atom, if all worked platformio-ide-terminal should just work. |
have a same error. trying that latest fix/release. |
Incase anyone is still struggling with getting platformio-atom-ide running on a mac, I was able to get it running on my MBP (v10.14.6) by downgrading Atom to (v1.28.2) using https://atom.en.uptodown.com/mac I had to click on the little "bug" icon on the bottom right to rebuild platformio-atom-ide (I had disabled/uninstalled) for compatibility issues it when I was trying to get it to work on Atom (v.1.39.1), then rebuild Atom. Finally, re-install platformio-atom-ide and it's working again. Aside: I was worried that it by downgrading Atom it would wipe all my settings preferences but thankfully it didn't. Hope this helps! |
I've managed to install the package on linux by following these steps: |
@rkdass see #707 (comment) that was for macOS also downgrade to 1.28.2, you meant 1.38.2, but thats not really a solution. you can try also #707 (comment) re: https://github.com/pfitzseb/node-pty-prebuilt/releases/download/v0.8.1-prebuilt3/node-pty-prebuilt-v0.8.1-prebuilt3-electron-v69-darwin-x64.tar.gz |
Rebuilding the packages (as offered in Atom after clicking the bug icon) worked for me, thanks! |
There is blocker issue https://github.com/daviwil/node-pty-prebuilt I'm not sure that @daviwil will fix it soon. Please switch to PlatformIO IDE for VSCode which has a built-in terminal. |
|
Mac OS/OSX FixFor me, it was a problem with I managed to install this package on the latest version of Atom (v1.39.1) on Mac OS using the following steps:
Hope this helps someone |
the above solution did not work for me. This bug really suffers me and I waste a long time today. I hope this will be solved as fast as possible... |
This solution works for me on Mac.
> apm install [email protected]
> apm install [email protected] |
@utotch Its your choice of course to stay with Atom 1.38.2 but platformio-ide-terminal should be version 2.9.1. |
Because the combination above is the only way to start up Atom successfully in my environment. Of course I wanted to use the recent version of Atom and plugins as far as possible. I was really tired to solve this problem because I couldn’t work almost a whole day and waist a time. sad. |
OK once @ivankravets merges #753 and makes a release we can all go back to work without disruptions. If that doesnt work for everyone else, I have no other solution at this time. Redirect issues related to node-pty-prebuilt-multiarch to https://github.com/oznu/node-pty-prebuilt-multiarch/issues |
Solution
There is blocker issue https://github.com/daviwil/node-pty-prebuilt
I'm not sure that @daviwil will fix it soon. Please switch to PlatformIO IDE for VSCode which has a built-in terminal.
[x] I have reset Atom to defaults prior to submitting report.
Description
It cannot be installed into Atom 1.39.0.
Maintainer EDIT
This ticket WILL NOW be used for discussions of issues related to the project and dependencies and other related information.
Fell free to add your considered thoughts and opinions below. Any offtopic, aggressive or otherwise inflammatory posts will be hidden or possibly deleted depending on the nature of post contents. This is because of trying to foster healthy discussions.
We are all project users all suffering from variants degrees of frustration, Its OK to vent in a considerate manner, anything else is not productive.
The text was updated successfully, but these errors were encountered: