Oldřich Jedlička
Oldřich Jedlička
/remove-lifecycle stale
Are you using `worker_hijack_root_logger=False` in the Celery setup? It seems this feature is not compatible with custom logger setup, so we had to disable it in our project. See also...
But if you are talking about OpenTelemetry logs forwarding, which is done through the root logger handler, the `worker_hijack_root_logger` value is important. If it is `True` (default), the OpenTelemetry handler...
The original issue from @giacomorebonato seems to be in `vite-plugin-pwa` actually, see [here](https://github.com/vite-pwa/vite-plugin-pwa/issues/798). The missing `createViteRuntime` reported by @martinkruusement is a real Vite 6 compatibility issue when `useViteRuntime` is `true`:...
@cyco130 is this project dead?
> In my opinion, the long-term solution to this is to avoid defining any environment variables at all in the application container, and instead write our configuration to a file....
> > This looks a way to go, but still the user can set env var [OTEL_EXPERIMENTAL_CONFIG_FILE](https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/1060#issuecomment-2440695054) (users are doing it already), in which case the auto-instrumentation's definition gets into...
It seems that the original solution with `$(JAVA_TOOL_OPTIONS)` is now reverted in favour of replacing the values. Maybe [my approach](https://github.com/open-telemetry/opentelemetry-operator/pull/3373) is not that bad? It looks to me that it...
I also had connection issue with mirrored mode, update to wsl 2.6.1 (with `wsl --update --pre-release`) fixed the issue for me. Thanks for the pointers, @CallisteH, I just figured out...