-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gulp stops running after some time (El Capitan upgrade) #52
Comments
That's weird. I can't think of something that could break without throwing errors after the update, so two questions:
Thanks! |
I know! Very strange. Answers:
Thanks! |
I'm currently running El Capitan here so I'll give it a try and report back. |
Good stuff. Indeed I'm hoping to find something consistent at the moment as well. Can you think about how I'd go about completely removing the package? Is it just a matter of deleting the package's folder, or are there other bits kicking around that I need to be aware of? I was thinking that it might be worth starting from scratch. |
Good idea! Deleting the folder should be enough. If you have custom user settings you could delete those too ( |
Hmm unfortunately that doesn't seem to have helped! I've removed and reinstalled and deleted the cache. Still can't find a pattern as to why it stops working. There's another issue that I've been having since upgrading to El Capitan: wbond/package_control#1002 (comment) Do you think that could be related? |
I don't think so because is related with crypto and I'm using the basic Sadly I couldn't reproduce the bug yet and I have little free time lately because I'm behind schedule in some paying work but I'm slowly working on it (that said, if you find a specific way to replicate the bug, let me know!) |
Ok, fair enough! I'm under it with client work at the moment as well! I'll let you know if I find a way of reproducing it. |
I'm having a wee problem with the Gulp package after upgrading to El Capitan.
On launching ST3, the Gulp package works as normal, but after some time, it stops working and new calls no longer bring up the list of tasks. No error message is displayed.
Any idea what might be going on?
Thanks!
The text was updated successfully, but these errors were encountered: