Didn’t found the syntax for the branch, I must be blind.
Anyway, I suppose that an entry in the config file to specify the branch is required, I’m not sure that we don’t want default branch everytime.
Thanks.
Didn’t found the syntax for the branch, I must be blind.
Anyway, I suppose that an entry in the config file to specify the branch is required, I’m not sure that we don’t want default branch everytime.
Thanks.
[quote=“bizoo”]Didn’t found the syntax for the branch, I must be blind.
Anyway, I suppose that an entry in the config file to specify the branch is required, I’m not sure that we don’t want default branch everytime.[/quote]
I think that having Package Control only pull from default when you specify a BitBucket URL is perfectly fine. If you want to use a version in a branch then you can clone the repo, checkout the branch and Package Control will keep it up to date with the remote for you.
Oups (on upgrade command):
startup, version: 2117 windows x64 channel: dev
...
Exception in thread Thread-4:
Traceback (most recent call last):
File ".\threading.py", line 532, in __bootstrap_inner
File ".\Package Control.py", line 500, in run
File ".\Package Control.py", line 300, in get_packages
KeyError: 'changesets'
This is the JSON I receive, no ‘changesets’ records
{
"node": "3bd4e612ff6e",
"files":
{
"type": "added",
"file": ".hgignore"
},
{
"type": "added",
"file": "Default (Linux).sublime-keymap"
},
{
"type": "added",
"file": "Default (OSX).sublime-keymap"
},
{
"type": "added",
"file": "Default (Windows).sublime-keymap"
},
{
"type": "added",
"file": "case_conversion.py"
}
],
"raw_author": "Scott Bessler <scottbessler@gmail.com>",
"utctimestamp": "2011-09-15 01:00:39+00:00",
"author": "scottbessler",
"timestamp": "2011-09-15 03:00:39",
"raw_node": "3bd4e612ff6ea1c865772a971fb517cc42f386f1",
"parents": ],
"branch": "default",
"message": "modifying case conversion to work on all selections, and pep8ing it",
"revision": 0,
"size": -1
}
I changed all:
last_commit'changesets'][0]
by:
last_commit
And apparently it works.
[quote=“bizoo”]Oups (on upgrade command):
startup, version: 2117 windows x64 channel: dev
...
Exception in thread Thread-4:
Traceback (most recent call last):
File ".\threading.py", line 532, in __bootstrap_inner
File ".\Package Control.py", line 500, in run
File ".\Package Control.py", line 300, in get_packages
KeyError: 'changesets'
[/quote]
I’ll get a fix out for that today. Thanks for the report.
Is this a package manger bug or sublime bug? When I start sublime and i’m not online I get an error box saying it couldn’t fetch the repository url and then sublime doesn’t load. I have to kill sublime in the task manager and start it again.
I’m not sure what the issue is there. I did just release version 1.2.7 so try to upgrade to that if you can. If you do continue to have problems, please open a ticket at github.com/wbond/sublime_package_control/issues since there is no notification system here on the forum.
As much as I like Package Control it throws a series of errors from time to time on ST2 startup.
The error it throws is:
Package Control: Error downloading repository. HTTP error 503
downloading
INSERT URL OF WHATEVER PACKAGE IT'S FAILING TO LOAD
Any suggestions as to what’s going on and how to fix it from freaking out?
[quote=“aple”]As much as I like Package Control it throws a series of errors from time to time on ST2 startup.
The error it throws is:
Package Control: Error downloading repository. HTTP error 503
downloading
INSERT URL OF WHATEVER PACKAGE IT'S FAILING TO LOAD
Any suggestions as to what’s going on and how to fix it from freaking out?[/quote]
A 503 error means that the service is temporarily unavailable. The way to work around it is to tell me you are having the problem, at which point I’ll look into enhancing the retry functionality to handle 503s in addition to timeouts. Is it GitHub that is triggering the 503s? What platform are you running on?
I’ll try to do this later today. Hopefully in the near future I’ll also be rolling out a centralized cache of package info that will help prevent issues like this, but also drastically improve the performance of Package Control.
I’ve been having a similar issue, using OS X Lion 10.7.1 and the latest dev version of ST2. This error pops up on start:
When I do Package Control: Discover, the error pops up again, and if I hit enter on any of the packages, it freezes ST2.
edit: I went in and removed SublimeLinter from Package Control Settings - User (there were two entries – even when I removed one it was still giving the error). Once I removed both of them, and re-installed SublimeLinter using Package Control, it worked fine. I remember the previous time I installed it, I had to enter the Git URL myself. Now I just have this in my User Settings file:
{
"auto_upgrade_last_run": 1316267222,
"repositories":
"https://github.com/buymeasoda/soda-theme"
]
}
[quote=“natebeaty”]I’ve been having a similar issue, using OS X Lion 10.7.1 and the latest dev version of ST2. This error pops up on start:
When I do Package Control: Discover, the error pops up again, and if I hit enter on any of the packages, it freezes ST2.[/quote]
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.
If this is not the case, please open a ticket on GitHub at github.com/wbond/sublime_package_control/issues. Unfortunately this forum isn’t a very good place for bug reports since there is no notification mechanism.
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.
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!
[quote=“aple”]
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! [/quote]
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.
I upgraded my packages, got a load of popups, and now get this message when trying to start SublimeText. I no longer starts up
http://dl.dropbox.com/u/497583/screenshots/SublimeText.png
That was using ST2 Build 2150. I’ve updated to Build 2151 but no change.
EDIT: Fixed it by following this https://forum.sublimetext.com/t/unable-to-run-package-setup/3350/4
[quote=“firefusion”]I upgraded my packages, got a load of popups, and now get this message when trying to start SublimeText. I no longer starts up
http://dl.dropbox.com/u/497583/screenshots/SublimeText.png
That was using ST2 Build 2150. I’ve updated to Build 2151 but no change.
EDIT: Fixed it by following this https://forum.sublimetext.com/t/unable-to-run-package-setup/3350/4[/quote]
Do you recall what the popups said?
Here are the instructions for future users to solve startup problems:
Win: C:\Users{username}\AppData\Roaming\Sublime Text 2\Installed Packages\
OSX: /Users/{username}/Library/Application Support/Sublime Text 2/Installed Packages/
Linux: /home/{username}/.config/sublime-text-2/Installed Packages/
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.
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).