i think this is the one https://github.com/typelevel/cats-effect/runs/1018303390?check_suite_focus=true
thankfully actions keeps track of every workflow run
it seems like like all the tests passed and then got stuck before running mima checks
this used to happen a lot
what causes it is the underlying Azure Pipelines instance going away
when that happens, teh build just... hangs roughly forever
that sounds like what happens
Beyond that, I discussed with @marcraminv the contents of the current TCP echo server - concurrent system with Fibers section. And we conclude that most of it is hard to read and understand. As I'm the author it pains me to admit it :) , but it is likely we should replace it with something easier to follow. E.g. we considered implementing a solution for the producer-consumer problem. What do you think?
Producer-consumer seems a lot easier to follow! Like, I love the TCP echo server concept, but it's definitely difficult to follow and requires some setup.
Something I've struggled with sometimes is whether or not it's worth referencing ecosystem projects
Like, you wouldn't implement a TCP server from scratch with vanilla CE, you would use another library which builds on top of CE and exposes that kind of fucntionality, then you would implement an echo server
depending on what you want to do
fs2 allows a very high level and composable api for dealing with concurrency
basically, you want to spend your time writing business logic, not writing concurrency-safe low level stuff
Yeah I have an aws client as resource that is pushed in from the top level. I need to use that resource in my business logic. One part of the business logic can be executed concurrently (which makes use of the above resource). So I want the resource to be freed only when the concurrent task also is completed. What are other options than start? I tried
background get back the concurrent execution as a resource. That also is not completing the work somehow.
Does it have to be released before your app closes? Not appropriate to open/close on init/shutdown?
If it's something like an http4s client, you absolutely want one for the whole process lifetime
(it does connection pooling, keep-alive, etc)
most resources you want to construct once and then pass down to your app already-alive
it's relatively rare that you really want to be dealing with
Resource inside your biz logic
I'm aware of
cats-mtl, but what if you need to eventually provide a context and convert reader-like G to a non-reader F?
i usually use the former, and usually add
trait Train[F[_]] {
def toot(): F[Unit]
def mapK[G[_]](f: F ~> G): Train[G]
}(cats-tagless can auto-generate these also)
sorry, i must be missing something
there's using
Kleisli vs. ApplicativeAsk, that's one choice
I'm now working in a project where "tagless-final-to-the-max" approach was taken.
There is always different types for
Lots of custom
Oh, and it uses doobie, so add another two types - one is instantiated to
There is always different types for
Fs with different contexts.Lots of custom
Lift/Unlift classes for conversion back and forth.Oh, and it uses doobie, so add another two types - one is instantiated to
ConnectionIO and second to Kleisli[ConnectionIO, ...], both with its own lifts-unlifts
So I wanted to know if its usual approach or not
is there some intermediate type like
class BizLogic[F[_]](alg1: Alg1[F], alg2[Kleisli[F, Dependency]])? because something like that would be difficult.
or at least more complicated than it probably should be. but i'm just guessing because i'm not sure of the structure you are describing.
typical signature is
def withRequestId[F[_], G[_] : WithRun[*[_], F, RequestId[F]](routes: HttpRoutes[F]): HttpRoutes[G]