Ben Carter

facing the same problem. Have you found a fix? Update: got it working. had the wrong build directory as a flag, was `/build` but changed to `build`. ```yaml - name:...

As a workaround you can either `export COMPOSE_COMPATIBILITY=true` in your bash profile or disable V2 in the Docker settings.

so from digging around it looks like the observed behaviour doesn't match the intention of the "always" strategy. https://github.com/scala-steward-org/scala-steward/blob/996af6a8b62b210637ba5fccc37d073f7131f6e2/modules/core/src/main/scala/org/scalasteward/core/nurture/NurtureAlg.scala#L275-L292 This code suggests if the strategy is `always` it will update...

Yes, this is running on Github.com. The workspace is persistent between runs, ScalaSteward closes old PRs. > For grouped updates the rules are slightly different In what way?

Failing binary compatibility: ``` method ioRetrying()org.scalatest.enablers.Retrying in interface cats.effect.testing.scalatest.AsyncIOSpec does not have a correspondent in current version ``` So it's the naming - not sure whether to rename it `ioRetrying`...

@sh0hei I think you approved the last build, is it possible to approve again?

@sh0hei any chance you can run the build? Otherwise if this is deemed no longer necessary I can close it.

I am trying to disable tracing from one framework but keep the metrics enabled. would this be possible through the metric view? Or would I need a custom Sampler as...

Is there any update on this PR's progress? Is something blocking it or does it need reviewing?

Very late to the party but I am trying to configure metrics for server connections using the `ServerTransportFilter`. I think at the very least it would be useful to expose...