microsoft / microsoft/TypeScript-Sublime-Plugin
Getting Package Control errors on OS X but command runs fine
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 236
- Avg merge
- 21d 13h
- Merged PRs (30d)
- 1
Description
I am receiving the following two errors whenever I start Sublime Text 2:
Package Control
Error executing: /usr/bin/git symbolic-ref -q HEAD
Working directory: /Users/NobleUplift/Library/Application Support/Sublime Text 2/Packages/TypeScript
Invalid connection: com.apple.coresymbolicationd
VCS-based packages can be ignored by changing the "ignore_vcs_packages" setting to true.
Sublime Text will need to be restarted once the setting is changed.
And:
Package Control
The process git seems to have gotten stuck.
Command: /usr/bin/git symbolic-ref -q HEAD
Working directory: /Users/NobleUplift/Library/Application Support/Sublime Text 2/Packages/TypeScript
This is likely due to a password or passphrase prompt. Please ensure git works without a prompt, or change the "ignore_vcs_packages" Package Control setting to true.
Sublime Text will need to be restarted once these changes are made.
When I cd "/Users/NobleUplift/Library/Application Support/Sublime Text 2/Packages/TypeScript" and run /usr/bin/git symbolic-ref -q HEAD, it returns refs/heads/master. I don't see where the plugin errors are coming from.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing /usr/bin/git symbolic-ref -q HEAD in the reported TypeScript package directory and compare the result when launched by Package Control. The issue names no repository file or test, so first determine whether the failure belongs to this plugin or to Package Control. Done means identifying a project-specific cause and a documented, reproducible resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100