Description

All recent continuous integration appveyor builds have failed due to trying to install an unmet mavensmate-atom dependency. This problem has persisted in the last three months (as far as I can tell). This defeats the purpose of CI because you get only false-negatives.

Input Before Beautification

N/A

Expected Output

Continuous integration build process continues

Actual Output

Installing mavensmate-atom to C:\Users\appveyor\.atom\packages failed

npm ERR! code E400
npm ERR! 400 Bad Request: https://www.atom.io/api/packages/mavensmate-atom/versions/1.1.0/tarball

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\appveyor\.atom\.apm\_logs\2019-09-03T21_52_05_534Z-debug.log

Command exited with code 1

Steps to Reproduce

Trigger continuous-integration/appveyor/pr by submitting a PR to Glavin001/atom-beautify or making a commit to the repository.
Wait for build to run
View appveyor status details

Debug

Here is a link to some of the most recent appveyor builds for this repository, all failed because of the above problem: https://ci.appveyor.com/project/Glavin001/atom-beautify/history

Looking into this further, the MavensMate project seems deprecated: https://github.com/joeferraro/MavensMate-Desktop And mavensmate-atom is non-existent: https://github.com/joeferraro/MavensMate-Atom

Checklist

I have:

[ ] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ ] Reloaded (or restarted) Atom to ensure it is not a caching issue
[x] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues so I know this is not a duplicate issue
[x] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

Glavin001 / atom-beautify

CI appveyor fails on mavensmate-atom dependency #2405