-
Notifications
You must be signed in to change notification settings - Fork 387
Open
Labels
P2We'll consider working on this in future. (Assignee optional)We'll consider working on this in future. (Assignee optional)help wantedNeeds help from external contributorsNeeds help from external contributorstype: feature requestNew feature or requestNew feature or request
Description
Here's an error message I observed:
╰─>$ bazel run //ip/wb/...
2025/07/13 12:45:32 could not resolve the version '# LICENSE sha256: c71d239df91726fc519c6eb72d318ec65820627232b2f796219e87dcf35d0ab4' to an actual version number: Invalid version '# LICENSE sha256: c71d239df91726fc519c6eb72d318ec65820627232b2f796219e87dcf35d0ab4'
Turns out that the issue was that I added the above comment into .bazelversion. All well and good, and justified - but it would be nice to have bazelisk print a prefix that explains which program printed the error, to make this less ambiguous. It would also be nice if the "could not resolve the version" explains where problem string is coming from (in this case, from .bazelversion)
Metadata
Metadata
Assignees
Labels
P2We'll consider working on this in future. (Assignee optional)We'll consider working on this in future. (Assignee optional)help wantedNeeds help from external contributorsNeeds help from external contributorstype: feature requestNew feature or requestNew feature or request