-
Notifications
You must be signed in to change notification settings - Fork 210
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
invalid user-provided repo name '' #883
Comments
bzlmod support is still in progress. Will ping back when it's working. |
any progress on this? |
@vadym-sedna I think the reason this may be happening is that bazel 6.0.0 was just released, and |
It looks like this is not correctly skipped with bazel 6.0
|
That is very odd -- python has always considered an empty string to be false. |
The starlack specs indeed states:
https://github.com/bazelbuild/starlark/blob/master/spec.md#booleans The current code should work but we clearly see it passes the condition 🤔 am I missing something? |
Till then, this seems like a reasonable work around. |
No longer an issue in 1.8 |
I'm trying to use this rule and I simply want to use the default compiler and toolchains. So I added this in my WORKSPACE:
but once I build, I have the following error:
This is seems weird to me because I check intialize.bzl where it uses
rules_repository
and I can't figure out where the repo name could be wrong.Edit
This is in the context of bzlmod. Apprently bzlmod has stricter repository name validation (ref)
The text was updated successfully, but these errors were encountered: