SeRGiOJoKeR11

Any joy on this issue? Although I am using this lib extensively in a service it only fails for me in an integration test. Very odd. I have tried many...

Yes, I have. @rcdmrl

Sorted. The problem is sbt default class loader layering strategy doesn't play very well with libraries using reflection. i.e kafka-[avro/schema]-serializer does use reflection. On this scenario, the sbt docs advise...

As of 0.23.10 I guess there is no fix for this issue, is that right? What is the preferred workaround? Would you recommend switching to a different server impl?

Please, my organization is holding on this. Could anyone have a quick look?

@RignonNoel in the meantime, I had to publish the package in order to unblock my team. Feel free to use it, it is public. https://www.npmjs.com/package/@flexys/ngx-translate-po-http-loader

@RignonNoel is [this](https://github.com/biesbjerg/ngx-translate-po-http-loader/pull/26) the PR that addresses this issue? A related concern. This library seems a bit abandoned and people are still using it. What shall we do about it?

> Agreed. I just installed it then checked the issues, and now I'm uninstalling it without ever getting started. @bluebaroncanada It doesn't mean the library doesn't do its job -it...

As a workaround, we base64 binaries before placing them in Secret Manager - this is not something the GCP UI does when using the file picker - then, the secret_data...

My brain doesn't retain information for very long. So, help yourself! ``` import cats.implicits._ import io.circe.syntax.EncoderOps import io.circe.JsonObject import scala.util.Try object JsonUtils { def removeValue(json: JsonObject, path: String): JsonObject =...