chore: include extra diagnostics when hermit decides not to activate #102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've observed hermit not activating on projects where it should. (specifically an internal Bazel project)
The problem appears to be in resolving the bin directory properly. (
guessProjectDir
seems to be returning a directory other than the repository root)This change outputs where it was trying to find hermit when it decided it wasn't a hermit project.
eg for a problematic project java, outputs: