Guillaume Onfroy

We've also been facing issue for a couple of months now with the grpc-health-check API resulting in the readiness probe failing on Kubernetes. The occurence of the problem isn't consistent...

@konstin There is a point from the original question that is not being addressed in your example which is that the packages should share the same namespace name (here `cable`)....

Well, you do need unique names under `[tool.uv.sources]`, right? So it cannot reflex the following structure: If we keep the same example, the tree would be: ``` ├── packages │...

Adding the following to the packages's `pyproject.toml` does solve the build issue, which makes sense. ``` [tool.hatch.build.targets.wheel] packages = ["src/cable"] ``` Which then allows to use a shared root namespace.

@rasheedamir You do have a `OpenShift` dependency (`route.openshift.io/v1`) [here](https://github.com/stakater/Forecastle/blob/master/deployments/kubernetes/forecastle.yaml#L252).

We've been using Dagster for a while in production now, and we find the lack of multi-threaded executor very painful on a regular basis. The multi-process executor can result in...

The multiprocess executor spin off... processes. Which essentially, AFAICT, always loads the entire project definition, hence the issues mentioned above. It doesn't seem to me that anything based on the...

Could be related to https://github.com/argoproj/argo-workflows/issues/6790? @alexec

@sarabala1979 Or `workflow.parameters` as mentioned above.

@sarabala1979 I did some more testing and I think I drilled down to a more specific diagnostic that my example above doesn't show. The problem seems to occur when both...