Scott Minor

Seeing this same issue, at exactly the same time in our repo. It seems like a server-side change has broken builds from otherwise-unchanged source.

Additional context: we have two repos ([repo A](https://github.com/enfabrica/enkit) and internal repo B) Repo A actually works after `bazel clean --expunge && bazel query 'deps(//...)'` - the above issue is NOT...

More context: compute library was indeed made a module yesterday: https://github.com/googleapis/google-cloud-go/pull/5273

Found a workaround - add a build_directives attribute to the `go_repository` rules that depend on `cloud.google.com/go/compute`, like: ``` go_repository( name = "org_golang_x_oauth2", importpath = "golang.org/x/oauth2", sum = "h1:pkQiBZBvdos9qq4wBAHqlzuZHEXo07pqV06ef90u1WI=", version =...

Upon further testing, it looks like the first case works because moves generated via `ChessMove::new()` are not validated to be legal, while ones from SAN are. The SAN en passant...

Examining [this loop](https://docs.rs/chess/3.2.0/src/chess/chess_move.rs.html#325) a bit more, where the parsed SAN is being checked against the full list of legal moves - if the SAN is assumed to be valid (say,...

+1 on data available through BES, or streaming through some remote protocol. There's already a good deal of challenge around getting the bazel client to perform well (in the face...

> @minor-fixes Adding "examples" to .bazelignore at the root would avoid Bazel recursing into that directory Thanks! I don't know why I expected the presence of a `WORKSPACE` file in...

I started with creating bindings in the sample application actually - and reversed course after I realized that I'm not sure what the long-term ramifications of doing specifically that for...

> I don't really have any idea how to test this, so we may find that it's necessary to roll back if it turns out to break someone. Can you...