I'm still missing something. I thought I had solved my problem of
overwhelming Postgres by using buffer(), but today (after upgrading to
2.4.2-RC3, but that's probably coincidence) I am getting a lot of timeouts.
As you can see below, I have two Slick sources, one nested via
flatMapConcat.
Even wi
I've migrated and everything compiles except the http route test. Tests
like the one shown don't compile, "route" isn't found.
it should "respond with handled = false for partial path" in {
Get(saPath) ~> route ~> check {
handled shouldEqual false
}
}
I don't see how to mig
Spoke too soon about snappy-flows.
ByteStringParser seems to have moved or disappeared between RC-3 and final.
I'll ping the author.
Caused by: java.lang.ClassNotFoundException: akka.stream.io.ByteStringParser
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
On Wed, Feb 17, 2016 at
Congratulations! I'm excited about this release, and I think if I could
Stream All The Things for the rest of my career, I would die a happy man :)
Migration note from RC3: IOResult and Framing have changed package. The
migration guide refers to the old location.
snappy-flows 0.1.2 (built with RC3
Thanks a lot! – A "humongous" thanks, I want to say :)
One question: will there be a release for Scala 2.10 (i.e.,
'com.typesafe.akka:akka-actor_2.10:2.4.2')?
– Hbf
On Wednesday, February 17, 2016 at 7:42:18 AM UTC-8, Konrad Malawski wrote:
>
> *Dear hakkers,*
>
> we—the Akka committers—are p
*Dear hakkers,*
we—the Akka committers—are proud to announce the FINAL RELEASE of Akka
2.4.2. The main change in this release is that it includes Streams & HTTP.
Some of these new modules are still marked experimental due to impending
API changes that we could not yet finish, in particular th
I am using the akka testkit TestEventListener to check for exceptions.
I have a number of test cases spread across the application that use it.
My application.conf for src/test looks like:
akka {
loglevel = "INFO"
loggers = ["akka.testkit.TestEventListener"]
But now, I get a TON of output in
If I were you, I'd use parallelism 1, and if that ever became a problem,
I'd revisit that choice.
Focus on the business value and tune when you have something which works :)
On Wed, Feb 17, 2016 at 11:49 AM, Alexey Shuksto wrote:
> Hello there,
>
> I have `Source[Future[T]]` which I need to tra
Hello there,
Is there a way to access run-time system configuration in
GraphDSL.create(...) similar to as any Actor could access one via
`context.system.settings.config`?
I can, possibly do something like `flow.zip(Source.repeat(config))`, but
maybe there is some approach that will not require
Hello there,
I have `Source[Future[T]]` which I need to transform to `Source[T]`
somehow.
Obvious choice would be to use `FlowOps.mapAsync(parallelism)(...)` but the
problem is -- I'm not quite sure how to determine 'right' `parallelism`
value -- basically I need mapAsync to produce as many f
We observe problems with both cluster sharding and cluster singletons.
With sharders - usually problem is corrupted journal that prevents sharding
coordinator from starting. In our situation easiest thing to do is to
delete all data from journal and restart it - problem is that I can't find
a wa
11 matches
Mail list logo