When I do Package Control: Discover, the error pops up again, and if I hit enter on any of the packages, it freezes ST2.

It looks like you have an improper repository URL to your installation, although I could be wrong. I don't believe Package Control ever uses URLs with .git at the end, which is why I think you may have added one. Please go to Preferences > Package Settings > Package Control > Settings - User. Delete any reference to SublimeLinter from your repositories setting. SublimeLinter is part of the default channel so you shouldn't need to add . If it was there, after you delete it you should not longer get a 404 (not found) error. You should now be able to install SublimeLinter.

wbond wrote:It looks like you have an improper repository URL to your installation, although I could be wrong. I don't believe Package Control ever uses URLs with .git at the end, which is why I think you may have added one. Please go to Preferences > Package Settings > Package Control > Settings - User. Delete any reference to SublimeLinter from your repositories setting. SublimeLinter is part of the default channel so you shouldn't need to add . If it was there, after you delete it you should not longer get a 404 (not found) error. You should now be able to install SublimeLinter.

Exactly how I fixed it (took me a second to figure out how to find that settings file). I guess I just posted this in case someone else had a similar issue.

Turns out this is user error, I thought I was supposed to copy/paste the repository URL, not the Git page URL (the same, but minus ".git" at the end). Maybe you should just strip /\.git$/ when a user does a manual Add Repository?

Anyway, was an easy fix. Thanks for the great package manager, such a fantastic addition to ST2.

wbond wrote:Is it GitHub that is triggering the 503s? What platform are you running on?

If I recall correctly, it is GitHub that's triggering these. Win 7

It's infrequent enough that it's not a huge issue, but when it happens it fires a bunch of them at the same time. Is there any way to simply make this silent and log it in an error log somewhere instead of throwing a bunch of alerts? I mean, how often do I really need to check GitHub now that I already have the packages?

Love the plugin though, blows every other IDE's package management out of the water. Thanks for the hard work!

wbond wrote:Is it GitHub that is triggering the 503s? What platform are you running on?

If I recall correctly, it is GitHub that's triggering these. Win 7

It's infrequent enough that it's not a huge issue, but when it happens it fires a bunch of them at the same time. Is there any way to simply make this silent and log it in an error log somewhere instead of throwing a bunch of alerts? I mean, how often do I really need to check GitHub now that I already have the packages?

Love the plugin though, blows every other IDE's package management out of the water. Thanks for the hard work!

Sorry for the long delay. Version 1.2.9 has handling built in to retry metadata requests that result in a 503. Hopefully this should reduce the number of popups you see.

This problem is caused by non-ascii filename being used in the package and the PackageSetup.py that comes with Sublime choking on it. I submitted a patch to Jon to fix some of these errors just a few days ago, but it looks like this is another. I'll send him another patch to fix this.

Funny story. I had installed SublimeCodeIntel again to give it another shot and maybe I would like it. It managed to slow my computer down and I decided to delete it. So I opened my packages folder and deleted it. I continue along for a couple of days and Sublime was giving me weird errors in the status bar. It said things like "Couldn't find language" so I figured their was something wrong with my tmLanguage file or something. I opened up my console and saw a bunch of references to codeintel. I thought to myself, "That's weird. I deleted that a while ago." So I went to my packages and there it is again. So again I deleted it. I relaunch ST and all is well. Then the errors start coming back. I look at my console and it says, "orphaned file found. Package Control reinstalling SublimeCodeIntel." So as it turns out, I needed to uninstall SublimeCodeIntel via Package Control.

TL;DR Package Control will reinstall packages that were deleted manually from the packages folder.

this may already be known, but PC isn't pulling the latest github version of SublimeCodeIntel. I noticed that in the json-package file for SublimeCodeIntel he hasn't updated the version number or modified date, so I'm wondering if PC just looks for a change in that version number to know to update from github.

defsquad wrote:this may already be known, but PC isn't pulling the latest github version of SublimeCodeIntel. I noticed that in the json-package file for SublimeCodeIntel he hasn't updated the version number or modified date, so I'm wondering if PC just looks for a change in that version number to know to update from github.

This is on purpose. To make sure everyone is using the same version of SublimeCodeIntel (to help with debugging, etc.), Package Control uses the latest stable version of SublimeCodeIntel (as deemed by the developers of SublimeCodeIntel).