-
Notifications
You must be signed in to change notification settings - Fork 402
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
Update version of io_bazel #195
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Liam,
I'd like to understand a bit more where it is coming from:
$ bazel query 'somepath(@io_bazel//tools/jdk:include/jni.h, //...)'
INFO: Invocation ID: 192a60e5-33c0-45f4-8472-3dc6c8d7712c
DEBUG: Rule 'io_bazel_skydoc' modified arguments {"shallow_since": "1544648677 +0100"}
DEBUG: Rule 'io_bazel_rules_sass' modified arguments {"shallow_since": "1542966119 +0100"}
DEBUG: Rule 'io_bazel' modified arguments {"shallow_since": "1543255285 -0800"}
INFO: Empty results
Loading: 0 packages loaded
io_bazel is not defined here, so there is probably something that is adding io_bazel as a repository somewhere in the transitive import.
Digging a bit into it.
I got it. This needs to be fixed on skydoc side. Maybe we should just switch to stardoc right now? |
Ok so I took a longer look and we should probably just update skydoc to a later version, bazelbuild/skydoc@7dccadb#diff-298c08b112de7c7b76694d16435c15a2 is probably the fix on skydoc side. |
I send #196 to update stardoc, I think this should fix the issue as stardoc is green itself. |
bazelbuild/bazel#7463