I'm new to working with akka-http and have a question that I hope someone
can provide some guidance with.
I've been trying to build my own custom directive - that would take the
results of an existing directive - perform some logic and then move onto
the next directive, or reject route.
For e
You need another data structure, look it
https://en.wikipedia.org/wiki/Bloom_filter
It is a probabilistic data structure that provide a efficient way to test
if a element is in a set or not. Useful to implement idempotent behavior
On Tuesday, August 18, 2015 at 4:36:36 PM UTC-3, Grzegorz Duszyńsk
I have a server, which on the one hand needs to send data and on the other
hands needs to receive data. So far I was unable to implement this.
The only code example, which I found, is this:
val tcpFlow = Tcp().outgoingConnection(host, port)
val bytes: IndexedSeq[ByteString] = ???
val resp
Hello,
I'm uncertain whether this is the correct place for my question since it
falls in the middle between Akka Streams, Slick 3.0 and Futures in Scala
but I will give it a shot. Please excuse me if you think otherwise.
First about the scenario. I have a flow whose purpose is to create some
a
I don't think so. I'm just testing the partial flows.
Nevertheless I never heard about what you're commenting but if that's the
case I think the Akka team have a good reason to do it. But if don't like
it I can always fork the code, that's the beauty of the open source ;)
Cheers,
Gabriel.
El l
If akka-actor is going to be removed from akka-stream wouldn't that impact
the ability to test the logic and functionality of your akka-stream code
with actor logic / messages?
On Mon, Aug 24, 2015 at 1:24 PM, Gabriel Volpe
wrote:
> I don't understand your question. What is the relation with the
I don't understand your question. What is the relation with the blog post?
El lunes, 24 de agosto de 2015, 19:13:00 (UTC+1), Adam Shannon escribió:
>
> I thought there were plans for akka-stream to move away from actors as the
> implementation detail. Is that still the case?
>
> On Mon, Aug 24,
I thought there were plans for akka-stream to move away from actors as the
implementation detail. Is that still the case?
On Mon, Aug 24, 2015 at 1:07 PM, Gabriel Volpe
wrote:
> Hi Akkers,
>
> I just want to share with you my new post! In this case I'm talking about
> how to design a full projec
Hi Akkers,
I just want to share with you my new post! In this case I'm talking about
how to design a full project using Akka Streams dealing with error handling
and ~100% test coverage. Also I created a demonstration project.
https://partialflow.wordpress.com/2015/08/17/akka-streams-designing-a
Hi,
thanks for this good explanation. Your solution works very well but an
explicit timout parameter would be desirable.
kind regards
Am Montag, 24. August 2015 15:13:51 UTC+2 schrieb Johan Andrén:
>
> .expectNext() uses a regular TestKit TestProbe behind the stage, and this
> has got a defaul
I've worked around this by starting an actor that polls a regular slf4j logger
and then changes the akka log level at run time through the event bus.
It works well enough, although it means selective log levels still incur a high
overhead, regardless of logging frequency and it also means that e
Guido, I agree with your advice.
I just wanted to mention the wrong conf property as additional info.
/Patrik
mån 24 aug 2015 kl. 17:23 skrev Guido Medina :
> And more information about the application itself to see memory usage
> patterns.
>
>
> On Monday, August 24, 2015 at 4:22:10 PM UTC+1, Gui
And more information about the application itself to see memory usage
patterns.
On Monday, August 24, 2015 at 4:22:10 PM UTC+1, Guido Medina wrote:
>
> Hi Patrik,
>
> I'm quite sure his problem has anything to do with Akka but lack of proper
> JVM parameters, that 32 seconds pause shown in his l
Hi Patrik,
I'm quite sure his problem has anything to do with Akka but lack of proper
JVM parameters, that 32 seconds pause shown in his logs would be enough to
cause nodes de-association and connection failures/timeouts of Akka remote
(without mentioning Akka cluster and other extensions) henc
Thanks for the update and the information.
On Wed, Aug 19, 2015 at 11:22 PM, craig bordelon wrote:
>
> Um, it looks like i had some issues with using 2.1 akka version of the
> example and not the 2.3 akka version needed.
> Also we learned that akka can do some things with ipv6.
> One must use []
Hi Rafał,
On Monday, August 24, 2015 at 3:49:57 PM UTC+2, Rafał Krzewski wrote:
>
> Oh, I see. OneServerPerSuite / OneServerPerTest traits must be really
> handy. Providing similar helpers for testing akka-http would be hard,
> because Play is a framework that mandates a well defined entry point
Oh, I see. OneServerPerSuite / OneServerPerTest traits must be really
handy. Providing similar helpers for testing akka-http would be hard,
because Play is a framework that mandates a well defined entry point and
configuration strategy, whereas akka-http is not.
Cheers,
Rafał
W dniu poniedział
Note that there is no: akka.cluster.transport-failure-detector
you probably mean: akka.remote.transport-failure-detector
The Disassociated might be triggered by that failure detector and you can
try to increase
akka.remote.transport-failure-detector.acceptable-heartbeat-pause
/Patrik
On Fri, A
The reason why I would like to create a materializer per stream is
exception handling. Currently it seems not to be intended to have a single
exception handler per stream.
The Supervision.Decider is something like an exception handler which is
bound to the materializer. But when handling except
.expectNext() uses a regular TestKit TestProbe behind the stage, and this
has got a default timeout of three seconds. I'm guessing your http call
takes longer than that and that is why you get an error, in the non
stream-testkit-example you wait infinitely long for a result to appear.
I can't f
Thanks a lot for clarifying!
I missed the part that onComplete stops the chaining which when thinking
about makes sense.
And indeed recover is all I need if I want to stick to the chaining
Am Montag, 24. August 2015 14:28:46 UTC+2 schrieb Johan Andrén:
>
> Hi John,
>
> I think the Akka docs pr
To cover your actual question a bit better, every operation that returns a
new Future will pass on any success or exception, and any map or flatMap on
the way will be skipped in case of an exception.
Pretty much like regular exceptions but in an asynchronous context. If you
throw an exception
Hi John,
I think the Akka docs pretty much covers all of it actually, and was
written with a Java hat on, so it should be much easier for you as a Java
dev to read those than to look at the Scala-docs.
You basically have two options, and both are covered in the docs:
1. side effecting using on
Thanks!
Em segunda-feira, 24 de agosto de 2015 09:04:10 UTC-3,
mathe...@sagaranatech.com escreveu:
>
> Hello,
> I'm need bibliography suggestions in distributed systems. I would like
> understand hard concepts used by akka, like consensus algorithms, crdt,
> algorithms applied to distributed sy
Here's some of my todo-list: https://www.wunderlist.com/lists/123387810
(rather slugishly updated)
You can also browse through the archive of http://sckrk.com (a reading club
we run in Kraków), there's a number of very nice ones in there.
On Mon, Aug 24, 2015 at 2:02 PM, wrote:
> Hello,
> I'm ne
Hello,
I'm need bibliography suggestions in distributed systems. I would like
understand hard concepts used by akka, like consensus algorithms, crdt,
algorithms applied to distributed systems. Can be books, papers, or
anything relevant correlated material. Thanks.
--
>> Read the d
Hi,
I am experiencing the same problem. My graph randomly suspends many minutes
after starting and waits forever. I see the same log and think that it may
be related to the problem. The code below retries requests indefinitely.
But it seems that in some situations Future does not fail but just
They should not I am just curious: there is a section of testing with
browser in Play docs (
https://www.playframework.com/documentation/2.4.x/ScalaFunctionalTestingWithScalaTest#Testing-with-a-web-browser
), maybe somebody wrote a similar example about testing akka-http with
browser
2015-08-24 12
Hey yeah the PR will greatly help.
Also any chance about the second question? How to generalize my
Broadcaster? So that I have one Publisher and get a multiple publishers
out? (specifiable by the number)
Am Samstag, 22. August 2015 18:42:55 UTC+2 schrieb Konrad Malawski:
>
>
> Somehow Google po
Why would Selenium tests of application using akka-http be different from
tests of application using any other server-side stack?
Cheers,
Rafał
W dniu niedziela, 23 sierpnia 2015 18:56:59 UTC+2 użytkownik Anton Kulaga
napisał:
>
> Hi all,
>
> I wonder, are there any examples of apps with Seleni
Hi,
For example I'm using:
scala.concurrent.Future responseFuture =
Http.get(system).singleRequest(request, materializer);
and then
Future newFuture = responseFuture.flatMap(new
Mapper>() {...}
If I want to handle the StreamTcpException should I register a OnComplete
Handler on response
Hello,
We are using the SLF4J logger to log akka events. However I have been
unable to set log level from our log4j.xml config file, it only works if I
set it in our akka config file. As we have all other related log levels in
our system set from that file we would like to avoid separating the
32 matches
Mail list logo
