Maksym Ochenashko

Would it make sense to shape a test console around an ADT? We have this implementation in otel4s: https://github.com/typelevel/otel4s/blob/4b5f51093e3bb2fbb20914f901a5752a88d8e26c/sdk/common/shared/src/test/scala/org/typelevel/otel4s/sdk/test/InMemoryConsole.scala#L28 The ADT offers enough flexibility to test operations. P. S. To...

On the other hand, since `TestConsole` covers different scenarios, it might be worth exploring two different implementations.

Thanks for the report. It would be problematic to add SLF4J (or Logback) dependency to the core or sdk modules. However, `Console` usage has bothered me for a while. It...

The new 0.15.0 release will include a console replacement.

`ManagementFactory` API to implement: - [ ] getClassLoadingMXBean - [x] getMemoryMXBean. #4021 - [x] getThreadMXBean. #4031 - [x] getRuntimeMXBean. #4034 - [ ] getCompilationMXBean - [x] getOperatingSystemMXBean. #4033 - [...

Could you check poller/worker-thread metrics by any chance? They are available via MBean out of the box.

I've observed an increased CPU usage, too. ### Service A. Has traffic The CE 3.6 version was deployed at 09:05. CPU usage   ### Service B. Nearly zero traffic...

> Second, am I reading this right that when you deployed 3.6, suddenly a ton of actual work materialized on the work queues? We weren't using IO Runtime metrics before...

> I'd really love for this to land 🚀 - but I see there's been no comments for 4 months - @iRevive is this waiting on feedback or approvals, or...

The current implementation has some flaws. For example, writing a retry policy for the following scenario is complicated: an effect is completed successfully, but the value is worth retrying (e.g.,...