Victoria Dye

> @ossilator I appreciate that you think about these issues. > > But generating everything from scratch every time, that would be hell twice over. That's a nightmare. Too many...

Due to the [lack of OTel logging support in Go](https://opentelemetry.io/docs/instrumentation/go/), going with `trace2` for the time being. For future reference, JSON-ified OTel structures: https://opentelemetry.io/docs/reference/specification/protocol/file-exporter/#examples

Should be implemented after #48 (that fix will introduce a more robust framework for running schedules).

I think there's value in backfilling tests for some of the types/functions we have already (for example, we don't have _any_ unit tests of the subcommands, even though they should...

> As discussed on #16380, the potential benefits given the alternatives of doing this in a FUSE (or NFS-as-FUSE on Mac OS) file system or teaching bazel query to recursively...

Hello! I'd like to add a bit of context around why I submitted this, what I'm looking for, etc. w.r.t your comments. For some background: while I'm new to Bazel,...

Thanks everyone for the commentary/discussion! @newren: I noted in the full proposal that most Bazel rules (like `cc_binary()`) rely on having source files on disk, and it would be a...

> Would this be an option? This approach is almost identical to one of the ones I considered before opening this issue ("create a mode/option allowing `bazel query` to print...

@lberki > yeah, it's not a great idea I had, it's a preference of mine between two of your ideas I wasn't looking to take credit, just clarify that I'd...

> With all the talks in BazelCon around wrappers built on top of bazelisk and the plugin model they provide, couldn't we just use the magic method approach and do...