Traceback (most recent call last):
File "core.git_command in /Users/user/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package", line 103, in git
File "core.git_command in /Users/user/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package", line 297, in repo_path
RuntimeError: Window does not exist.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "core.commands.commit in /Users/user/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package", line 142, in <lambda>
File "core.commands.commit in /Users/user/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package", line 162, in run_async
File "core.git_command in /Users/user/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package", line 106, in git
File "core.exceptions in /Users/user/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package", line 7, in __init__
TypeError: GitSavvyError does not take keyword arguments
It happens across many repos. Not always though - one commit might be fine, another may fail (furthermore, it can fail twice and then work once). I’ll clone the repo to my Packages and add some debugging code. Will be back with more info.
I don’t think the files were that strange but I’ll definitely take more notice now. I found it weird that committing the files the second time around works fine, even without making any other changes.
I had initially suspected something wrong with my git because GitSavvy has been working fine for the past ~year I’ve been using it. I think this issue has only really appeared within the last few weeks for me.
I’ll try turning on logging to see if that reveals anything.