Nadav Wiener

@mdedetrich To clarify, I do not consider a single-core pthreads-based implementation a "model". A proper model would be like you propose—"freestyle" threading combined with a Java-like memory model. I was...

@binary132 Well, for one, pthreads provides finer-grained control than C++ threads does. Real time threads are still a pipe dream at this stage, but are one example of something pthreads...

I've been experiencing this in builds since at least may -- I guess it's been that way ever since nested containers were introduced?

Simply translating `dependencyOverrides` into `dependencyManagement` sounds straightforward and I'd be happy to contribute, but worried I'm missing something -- looking for pitfalls before I start. Can anyone familiar with this...

@johanandren Sorry for the late response—Google Inbox has been playing tricks on me again. I agree this would be sufficiently useful to justify including in the core library—I chose to...

@dvgica I looked into kamon-akka's reference.conf and tried disabling instrumentations to narrow down the root cause. I'm using Kamon 2.5.0 (didn't want to switch the otel reporter implementation yet), and...

@ivantopo This was probably introduced by #1135, so only Kamon 2.5.0 and later should be impacted. `Scheduler.scheduleOnce` wasn't instrumented before then. This answers my concern above -- since most of...

We are also encountering this while calling `dependencyTree` on 1.6.2. sbt 1.6.2 is quite old by now (we'll try to reproduce with recent versions), but I'm sure there are others...

@ptrdom Thanks for the swift reply, we're working under that assumption. Looks like it's more of a matter of "dependency amplification" for us (needless config mess causing more dependency sprawl...

I'm also experiencing this. Built against master (4e4b754) on Arch. I'm running Arch as a vmware guest, and each disconnect or connect event is listed twice. `udevadm monitor -u` only...