Matthew Kuzyk

I do have the same `BUILD` file specified by the tutorial. The error was reproduced by following the tutorial to the letter. Deleting that line is fine. When `bazel run...

This also mimics the workspace file in the official [Gazelle Go tutorial](https://github.com/bazelbuild/bazel-gazelle#setup)

Looks fine, though I'm not sure why it's necessary over the simplicity of letting Gazelle generate `deps.bzl` for you (which it will do when `bazel run //:gazelle-update-repos` is run)

Small followup, we are printing the `PipesMessageHandler` object and unsurprisingly for our long running failed jobs we can see it didn't receive a close message: ``` {'_context': , '_message_reader': ,...

We have learned a lot and have found what we believe to the crux of the issue. [In the `run` function](https://github.com/dagster-io/dagster/blob/a5ec87b7a5c6efb3cc26542cac43563468ce6d1e/python_modules/libraries/dagster-k8s/dagster_k8s/pipes.py#L273) of the `PipesK8sClient`, the main thread is blocked by...

Sorry for the late reply, I was out last week. We are working on a custom extension that would resolve this issue. We already have a custom extension for multi...

@danielgafni I could see the use in that. The only kube specific logic in the `merge_streams.py` code is to do with timestamp checking, but we can refactor that out to...

@danielgafni All I did for now was move the `merge_streams` logic to pipes and pass the `_process_log_stream` function into it as a generic callable that returns an iterator of log...

Hey @danielgafni, bumping this. Wondering if I should take this out of Draft and get more eyes on it. The main part that definitely feels WIP to me is the...

Hey @danielgafni, thanks for the update. We'd like to merge the PR as-is. If this code is updated later, merging it now won't incur additional work in the future. The...