Laurynas Tretjakovas

What about `ClassNames` and `ObjectNames`?

Would it make sense to manually map rules from Scalastyle and Scapegoat to tech debt metrics that would be defined inside this plugin?

I think the actual problem is on line 55: ```scala val errorStatus: StatusCode = cause.failureOption.flatMap(toErrorStatus.lift).getOrElse(StatusCode.UNSET) ``` If you change `StatusCode.UNSET` to `StatusCode.ERROR` then you don't need any additional attributes and...

> Aren’t you looking for `catchAll`? For `catchAll` you need to provide an alternative stream. And if that one can fail as well, it must also have an alternative stream....

Yes, I agree. Previously I worked with Akka streams and got used to [supervision-strategies](https://doc.akka.io/docs/akka/current/stream/stream-error.html#supervision-strategies), they are quite nice for the use-case, except that adding cleanup effects in deciders is cumbersome....

Another workaround is to do `sbt scapegoat || true`. This will ignore any errors and with the next command you can upload the report to SonarQube.

Just tested and this change would break `getOrElse` when the option type is `FreeS`, so maybe there should be another method `FreeS.purePar`.

Here is the manually constructed sink that helped with throughput ```scala Sink .foreachAsync[ProducerMessage[T]](300)(msg => producer.sendAsync[Task](msg).void.runToFuture) .mapMaterializedValue { completionFuture => val flushAndClose = for { _

> A proposed solution by @vroldanbet is to combine CREATE with an idempotency key. By doing this, if the WriteRelationships operation fails because the idempotency-key-relationship already exists, it would signify...

It's a shame that publishing to maven central is broken, because to pull an artifact from GitHub packages you must authenticate, so that needs to be done by every team...