Skip to content
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

Cache Key is not set when dependent repository targets a specific commit #366

Open
adduc opened this issue Apr 25, 2017 · 1 comment · May be fixed by #367
Open

Cache Key is not set when dependent repository targets a specific commit #366

adduc opened this issue Apr 25, 2017 · 1 comment · May be fixed by #367

Comments

@adduc
Copy link

adduc commented Apr 25, 2017

We use a few dependencies in our composer.json that target a specific commit (e.g. dev-master#4b7c20db3c72a859df049701db43659187bc4573). Every time VSCode starts, these dependencies are reparsed, even if no file has changed since the last time VSCode has started. Within the log output, this is seen:

[Warn  - 9:35:35 AM] Could not compute cache key for phing/phing

It looks like the cache key is decided in src/Indexer.php. When a version isn't used, could you cache off of the commit ID (if available)?

@felixfbecker
Copy link
Owner

Sound reasonable. Feel free to do a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants