Nice post, thanks for sharing! :-)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 7 November 2015 at 12:41:50, Gabriel Volpe (volpegabr...@gmail.com) wrote:
The previous project was updated and the changes were pretty straight forward.
https://partialflow.wordpress.com/2015/11/07/akka-s
Yes it should.
It's "delete messages to sequence nr 12".
We have tests for it in the TCK, but it's up to the Journal implementations to
corrently implement this.
Which journal impl are you talking about?
By the way, these things are very simple to check for yourself - just write a
test which do
one you
should be able to figure out how to translate your Flexi things.
There will be an M2 soon, then we'll explain in detail how to migrate from
Flexi things.
Hope this helps!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 7 November 2015 at 01:23:17, Konrad Mala
Hi David,
It's there already though :-)
Docs:
http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0-M1/scala/http/routing-dsl/directives/method-directives/patch.html
/**
* Rejects all non-PATCH requests.
*/
def patch: Directive0 = _patch
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Type
ry thank you, I should have looked better. I am just getting started
> and when looking for patch I might have been looking at some older
> documentation.
>
> Thanks
>
> On Tuesday, November 10, 2015 at 12:22:12 PM UTC-5, Konrad Malawski wrote:
>>
>> Hi David,
>&
Hi Gary,
(I think I replied to this already, but maybe you're only on scala-user and not
akka-user? Sorry for duplicated email everyone else).
yes, you should read the AsyncStage => GraphStage migration:
http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0-M1/scala/migration-guide-1.0-2.
Usually one would do something like this:
trait MyModelJsonProtocol extends DefaultJsonProtocol {
implicit val feedFormat = jsonFormat2(Feed)
}
object MyModelJsonProtocol extends MyModelJsonProtocol
And use it like so:
trait MyHelloWorldRoute extends MyModelJsonProtocol = {
val route = compl
Hi all,
thanks for trying out the early Milestone and reporting the problem!
We believe there is a bug in how the idle timeout was added, not sure if that
specific problem is a manifestation of it,
but we'll add more tests and fixes for idle timeouts in M2 (coming out soon),
please keep an eye ou
Hi Chris,
Jim responded quicker than I managed to; thanks! :-)
I'll add a bit more positive hints to the above suggestion,
it seems that BouncyCastle does implement the cipher you're after:
https://github.com/bcgit/bc-java/blob/dd3d4c4ffe31296e231e9075a26c72b399be3f05/core/src/main/java/org/bouncy
Play is not compatible with Akka Streams "2.0-M##" yet - it's a development
milestone, not a release you can expect all libs to be ready for already.
Please wait until Akka Streams "2.0" is released at which point Play will be
updated to work with it.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @
ork
> around the bug?
>
> On Fri, Nov 20, 2015 at 6:51 PM, Konrad Malawski
> wrote:
> > Hi Rudiger,
> > Yes it's a bug (two separate ones even, another thing you'll notice is
> > actors leaking).
> > And good news - we tracked it down and fixed it today! W
Hi Rudiger,
Yes it's a bug (two separate ones even, another thing you'll notice is
actors leaking).
And good news - we tracked it down and fixed it today! Will be released in
M2 which will be released early next week.
Thanks for reporting!
On Nov 20, 2015 18:47, "rklaehn" wrote:
> Hi All,
>
> I
Right; "this isn't rocket science" (-;
All feedback is very welcome though Rudiger, please let us know if anything is
non obvious or undocumented!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 20 November 2015 at 19:08:44, Konrad Malawski (konrad.malaw...@
Awesome reply, thanks Tim!
We also have this documented (though for spray-json instead of play-json) in
our docs here:
http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0-M1/scala/http/common/json-support.html
Hope this helps!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 22
Hi Jan,
sure!
Here's how:
http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0-M1/scala/http/routing-dsl/directives/debugging-directives/logRequest.html#logrequest
I recommend implementing the "show", so it shows nicely (and not a raw
bytestring as response body) while you're debugging
You should read up on cluster sharding:
http://doc.akka.io/docs/akka/current/scala/cluster-sharding.html
Such "to the same Actor, given an identifier" is exactly what it is designed
for.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 28 November 2015 at 11:59:52, Karthik Deivasigamani (
Hi Rob,
The marker trait NotInfluenceReceiveTimeout strictly works "for the given
message type".
You can not plug in logic as to when it should or should not influence the
receive timeout - it would be really tricky and weird to represent.
Instead you should model your timers explicitly, using `
Did you see:
# Enables/disables the addition of a `Raw-Request-URI` header holding the
# original raw request URI as the client has sent it.
akka.http.server.raw-request-uri-header = off
Perhaps it would address your need?
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 1 December 2015 a
nt and ran into some issues. So wanted to know if
non-persistent actors are supported.
Thanks,
Karthik
On Saturday, November 28, 2015 at 3:47:22 AM UTC-8, Konrad Malawski wrote:
You should read up on cluster sharding:
http://doc.akka.io/docs/akka/current/scala/cluster-sharding.html
Such &qu
On Thu, Dec 10, 2015 at 7:53 AM, Alan Johnson wrote:
> I'm new to this space, but yes, it seems to me like the read store should
> store lastProcessEventNr someplace, ideally updated in the same transaction
> that updates the view.
Welcome to the community then :-)
Yup, that's exactly the idea,
Hi Giovanni,
"We're working on it".
M2 has the parts needed to enable stream fusing.
Currently we're working on enabeling it for the most complex pipelines – the
Akka HTTP pipeline.
2.0 will be out before x-mas, it's a time based release.
We're expecting those changes to be in it.
We're not spe
We have not changed our build process so it's the same as a year ago, sure :-)
It is documented here:
http://doc.akka.io/docs/akka/snapshot/dev/building-akka.html including the
option to disable diagrams if you need to.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 10 December 2015 at
It's a feature. (yes, really) :-)
Allow me to explain; Akka HTTP always opts on the safe side of things.
For example, if you write an endpoint that can get POST data, and someone (an
attacker) sends you data and it never ends sending...
You do want to kill that connection as soon as you notice so
fine though.
Thanks,
Jeroen
Op vrijdag 18 december 2015 14:17:47 UTC+1 schreef Konrad Malawski:
It's a feature. (yes, really) :-)
Allow me to explain; Akka HTTP always opts on the safe side of things.
For example, if you write an endpoint that can get POST data, and someone (an
attacker)
Akka Streams since it
has hit 1.0 a few months ago:
commits added removed
8078222022 Konrad Malawski
7158031316 Johannes Rudolph
4252921142 Alexander Golubev
3279543082 Mathias
2739324035 Viktor Klang
26 106343554 Endre Sándor Varga
Correct, as has been forecasted for Akka itself in December 2014 –
https://www.typesafe.com/blog/akka-roadmap-update-dec-2014
and is the case for Akka 2.4.x currently – we require JDK8 moving forward.
The 2.0.x series of Akka Streams and HTTP is the last one available for
pre-JDK8.
We did both us
I'll leave the semantics questions to Roland or Endre to tackle (in general it
should not change semantics), but a few quick ones:
2. how to insert async boundaries in linear pipelines? E.g.:
Source(List(1, 2, 3))
.map(_ + 1)
.addAttributes(Attributes.asyncBoundary)
.map
FYI, Roland's docs update merged: https://github.com/akka/akka/pull/19268
I'll release 2.0.1 today as we found a bug in InputStreamPublisher.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 23 December 2015 at 09:14:58, Adam Warski (a...@warski.org) wrote:
:-)
But you are right, even th
You need the s1 and s2 values to "contribute to the materialized value of
graph".
Please read this section of the docs:
http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0/java/stream-composition.html
then:
http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0/java/stream-graph
Hi Jan,
please read about Akka Persistence.
>From your code snippet it's not possible to say if the events are persisted
under the persistenceId "persistentActor-4-java" or not.
What's the def persistenceId in the Actor look like?
What is not working in the example you pasted?
-- Konrad
On Wed,
Aclosed>
milestones on github for your reference.
Credits
We would like to thank Mathias Bogaert for swiftly trying out the latest
release and submitting a small improvement to HTTP’s domain model, thanks!
commits added removed
8 228 82 Konrad Malawski
3 619 38 Rolan
This sounds a bit weird... I don't think those changed that much in the move to
2.0.
Could you make the problem example a gist (gist.github.com or complete snippet
in email, ready to copy/paste) I could downlaod and quickly have a look? Thanks
in advance!
--
Cheers,
Konrad 'ktoso’ Malawski
Akk
Not built in but doable, see
https://github.com/movio/spray-dynamic-routing-example for inspiration.
You should be able to translate it to Akka HTTP.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 24 December 2015 at 10:17:23, greg.kam...@bcgdv.com (greg.kam...@bcgdv.com)
wrote:
Hi,
f
Grep the rederence.conf of Akka http core for 'idle-timeout'. We also have
it documented AFAIR, but not at my laptop now.
On Dec 24, 2015 15:00, "Richard Grossman" wrote:
> Hello
>
> I see that nobody answer to this
> Any news ?
>
> On Tuesday, November 10, 2015 at 8:04:37 PM UTC+2, Richard Gross
Sorry, I've misread your question - you mean a request-timeout.
I'm not sure from the top of my head, will revisit this after christmas
dinner.
I quickly grepped and it may be missing still, could you open a ticket for
this?
On Thu, Dec 24, 2015 at 3:02 PM, Konrad Malawski <
You're in a distributed system – how would you do it there?
"The Akka way" of doing it is messaging :-)
Send a message to the "cluster actor", which each JVM has,
from the same sender,
collect the replies,
once you got all of them (and you know, because you know how many questions
you've sent),
Without going much deeper – I certainly wouldn't add any of these to a project
just to get a CRDT counter ;-)
Also, we have those too:
http://doc.akka.io/docs/akka/snapshot/scala/distributed-data.html :-)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 25 December 2015 at 11:22:07, Guido
After having consulted a number of customers who included or previously-had
hazlecast clusters along with
Akka apps I remain unconvienced what hazlecast added to the table (other than -
"yet another cluster, with different
and detached lifecycle to manage"). I'd avoid adding more separate indepe
rovides distributed data, but it's
still experimental. Moreover, it doesn't seem to provide functionalities like
locking or queries. The data is also replicated on all nodes which can be too
much redundancies (or is it configurable?).
On Friday, December 25, 2015 at 8:13:18 AM UTC-6, Konra
API simplicity is one thing – runtime, failure and recovery semantics are
another, that's there the dragon lies.
My only point here is, that it's tricky to have 2 clusters being running in the
same jvm, because there's much more
failure scenarios you suddenly have to think about:
- what if Akka
But now, there's one thing that I'm not too happy about: both distributed
pubsub and distributed data seem to replicate all data onto all nodes instead
of spreading out to the cluster.
That's not true – pubsub only sends data to such nodes, which subscribed to a
given topic.
If all people are
.create() is a normal method on the companion - it should just work.
Did you find out what the problem was?
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 25 December 2015 at 01:19:15, Anton Kulaga (antonkul...@gmail.com) wrote:
Hi. I updated my project to akka-http-experimental 2.0.1 I
Hi Jochen,
The bounded mailboxes are designed around the idea that in Akka delivery is
at-most-once in any case (because network, and no re-delivery – unless you use
AtLeastOnceDelivery or do it yourself). So yeah, they're protecting the
receiver, nothing more - it's not a full-blown flow-contro
d your answers have
been great help. Thanks a lot!
Alex
PS. This seems to be very off topic from the original question. Should I start
a new thread?
On Monday, December 28, 2015 at 4:16:45 AM UTC-6, Konrad Malawski wrote:
But now, there's one thing that I'm not too happy about: both di
Please read up on the Akka Cluster documentation:
http://doc.akka.io/docs/akka/snapshot/java/cluster-usage.html
Quote:
The seed nodes can be started in any order and it is not necessary to have all
seed nodes running, but the node configured as the first element in the
seed-nodes configuration
Hi there,
You're the one creating the HttpResponse directly if you want to modify it, see:
import akka.http.javadsl.model.*;
return ctx.complete(
HttpResponse.create()
.withEntity(HttpEntities.create("example"))
.addHeader(Location.create("http://akka.io";)));
Happy hakking!
--
Cheers
I improved the docs slightly to show this style of completing as well:
https://github.com/akka/akka/pull/19350
-- Konrad
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Sear
Hi Arnaud,
Thanks for reporting.
Obligatory disclaimer: disabling hostname verification is a very bad idea,
please don't.
I looked into it and it's a mix of issues actually... ssl-config should be
improved, but that's not what's causing your error actually.
Since you're on JDK8, hostname veri
Do you have some collections involved in the pattern match perhaps?
Show us your receiveCommand / receiveRecover.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 5 January 2016 at 15:55:18, matheusl...@sagaranatech.com
(matheusl...@sagaranatech.com) wrote:
Sorry, I've read fast your code
Konrad, thanks for the quick reply. Our nodes are similar (receive same
traffic on same hardware). We have frontend and backend node roles (10 FE, 16
BE). Does 4 nodes (2 from each role) sound reasonable?
Seed nodes are just "the nodes to which a new node talks to in order to join
the cluste
They're on a branch, documented here currently:
https://github.com/akka/akka/blob/master/CONTRIBUTING.md#branches-summary
The branch is `release-2.3-dev`, it's exclusively for Akka HTTP and Streams
development while they were heavily experimental.
https://github.com/akka/akka/tree/release-2.3-de
It should work properly.
There was a PR refactoring that area, indeed:
https://github.com/akka/akka/pull/19066/files
Are you sure you don't have mixed up akka http dependencies or something like
that via messy dependencies?
You mention you looked at dependencyTree so that would show up there tho
ttps://github.com/rklaehn/invaliddependency
I will compile this from my home machine to check that it is not some local
configuration weirdness. But we have had this happen from two machines at
work...
On Tuesday, January 12, 2016 at 4:55:31 PM UTC+1, Konrad Malawski wrote:
It should work
<https://github.com/akka/akka/issues?q=is%3Aissue+milestone%3Ahttp-2.0.2+is%3Aclosed>
milestones on github for your reference.
Credits
commits added removed
6 287 76 Roland Kuhn
5 173 124 Konrad Malawski
2 99 4 Endre Sándor Varga
This may be a bug, I'll look into it soon so thanks for reporting!
Glad you liked the talk :-)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 15 January 2016 at 23:57:01, Gustavo Politano (gustavo.polit...@gmail.com)
wrote:
Hi!
I was watching Konrad's workshop from Scala eXchange - ama
Oh wait you should check
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-M2/scala/http/directives/file-and-resource-directives/getFromFile.html
I'm already in bed though ;)
On Jan 16, 2016 00:01, "Konrad Malawski"
wrote:
> This may be a bug, I'll look int
Have you tried?
s ~> Flow[Element].log("...") ~> thingy
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 20 January 2016 at 10:56:01, Richard Grossman (richie...@gmail.com) wrote:
Hi
When working with simple flows you can add between steps log directive. like
Flow.log("start").map
Technically it may be safe in that case, you're in an Actor after all.
However I'd argue it's bad style as it mixes an API designed for immutable data
passing (the data param of FSM),
in a mutable way, which can/will lead to confusion when someone else reads your
code.
If you want to have (or ar
1, James P (jsp0...@gmail.com) wrote:
Hi Konrad,
Thanks for the guidance, much appreciated! Good points, will try to stick to
immutable data params for FSM. Have a great weekend :)
On Friday, January 29, 2016 at 3:40:23 PM UTC-8, Konrad Malawski wrote:
Technically it may be safe in that case, yo
Sounds like you're asking about:
http://doc.akka.io/docs/akka/2.4.1/scala/cluster-sharding.html#Remembering_Entities
Have you seen that feature? :)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 9 February 2016 at 16:01:06, Paul Cleary (pclear...@gmail.com) wrote:
I am using Cluster Sha
Hi there,
this has been a hot topic for quite some time.
There exist attempts to implement it in the community, for example:
https://github.com/Tecsisa/akka-http-swagger
or https://github.com/devsprint/akka-http-swagger
For an in depth discussion why it's hard to implement see this issue:
https:
Hi RIchard,
there's a PR fixing this and the larger issue which is JDK8 types exposure in
that API.
Will be merged any moment now: https://github.com/akka/akka/pull/19636 for
2.4.2.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 15 February 2016 at 05:47:23, Richard Rodseth (rrods...@gm
Hi Matthieu,
Akka HTTP's low level is what it is – low level :-)
No, we don't provide any routing capabilities like this in the low level api.
Why don't you want to use the high level routing DSL? It has nice support for
those things built in.
If it's not an option, you can parse the Uri and ext
Hi Daniel,
Before I dive into your question I'd like to highlight that the Java directives
are undergoing an intense
rewrite just now (they're still experimental, so that's why we must do it now),
and will be way more elastic soon:
https://github.com/akka/akka/pull/19632/files?diff=unified
So i
bout production readiness too much and if we have to
rewrite a layer of the app then so be it.
Is there a SNAPSHOT/nightly build version or the likes where I can try out the
new DSL?
Thanks again,
Dan
On 15 February 2016 at 15:49, Konrad Malawski
wrote:
Hi Daniel,
Before I dive into your quest
Hi Richard,
Not that I'm aware of.
You can ping the library maintainer to upgrade to 2.4.2 (we're releasing
that today) though :)
On Tue, Feb 16, 2016 at 1:45 AM, Richard Rodseth wrote:
> I just had the rather gratifying experience of adding Snappy compression
> using snappy-flows with
>
> .via
Hi there,
Protocol buffers don't really works on "any case class", you have to map values
to protoc generated message classes,
(middle collumn in the example), whihc are generated from an IDL shows on the
left hand side column here:
https://developers.google.com/protocol-buffers/
Read up on how
Hi there,
the docs are:
https://github.com/akka/akka/blob/master/akka-docs/rst/scala/stream/stream-quickstart.rst
from there you can find the includecode snippets pointing to:
https://github.com/akka/akka/blob/master/akka-docs/rst/scala/code/docs/stream/TwitterStreamQuickstartDocSpec.scala
which
Hi there,
Could you share your configuration first and also how you're observing the
described problem?
Do you have a reproducer for this mesbehaviour?
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 16 February 2016 at 16:33:21, Hareesh Jagannathan (harjag...@gmail.com)
wrote:
Akka app
n Tue, Feb 16, 2016 at 2:16 PM, Endre Varga wrote:
Planned. Had not time so far :)
On Tue, Feb 16, 2016 at 2:15 PM, Viktor Klang wrote:
(Or add support for compression!)
On Tue, Feb 16, 2016 at 2:13 PM, Konrad Malawski wrote:
Hi Richard,
Not that I'm aware of.
You can ping the library mai
You may want to read my SO answer which explains what you're seeing somewhat
(including pictures and how to configure dispatchers properly):
stackoverflow.com/questions/34641861/akka-http-blocking-in-a-future-blocks-the-server/34645097#34645097
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
Errors only flow downstream.
So in order to take a downstream error and make it fail something "upstream"...
you'll have to connect that downstream to the upstream so it becomes a
downstream :-)
I hope that made sense :-)
In general though, you could make a fan-out operation from your downstream
*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'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 migr
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
It's rather weird if y
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 18 February 2016 at 10:46:42, Endre Varga (endre.va...@typesafe.com) wrote:
One question: will there be a release for Scala 2.10 (i.e.,
'com.typesafe.akka:akka-actor_2.10:2.4.2')?
No. The rule is and has always been that we release for "cu
Thanks for reporting, likely it's harmless if happened after timeout but
maybe we can make it note silent, please report as an issue, thanks!
On Feb 18, 2016 20:57, "David Knapp" wrote:
> After upgrading from 2.0.3 to 2.4.2, I'm getting this error when one of my
> requests times out:
>
> 2016-02-
Hi,
Have you tried setting akka.ssl-config.hostnameVerifierClass to your custom
"accept everything" classname?
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 19 February 2016 at 16:45:55, Michi (michael.tha...@physik.tu-muenchen.de)
wrote:
Hi,
I have written a small HTTPS test server
regards,
Michael
On Friday, February 19, 2016 at 4:55:56 PM UTC+1, Konrad Malawski wrote:
Hi,
Have you tried setting akka.ssl-config.hostnameVerifierClass to your custom
"accept everything" classname?
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 19 February 2016 at 16
#x27;ktoso’ Malawski
Akka @ Typesafe
On 19 February 2016 at 17:15:23, Endre Varga (endre.va...@typesafe.com) wrote:
Cannot the self-signed certs be added to the truststore though? That would be
the "proper" workaround.
-Endre
On Fri, Feb 19, 2016 at 5:12 PM, Konrad Malawski
wrote:
Current
Because Akka uses non-daemonic threads, so it'll keep the app running until you
shut-down the ActorSystem.
You can do so via:
import system.dispatcher
s.runForeach(println).onComplete { _ => system.terminate() }
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Lightbend
On 23 February 2016 at 18:11
Hi Gary,
it's as simple as setting a dispatcher for a Flow.
val flow =
Flow[String].via(myBlockingStage).withAttributes(ActorAttributes.dispatcher(“my-configured-blocking-dispatcher”))
(setting a dispatcher also implies an asynchronous boundary).
Of course try to avoid these blocking APIs, yo
Hey Rüdiger,
yeah those can definitely be used in all kinds of APIs.
The reason we have them mostly in Streams for now is because we could not break
compatibility in akka-actor for example.
The types are intended to be simply more informative than plain `Unit`, so
wherever that's needed feel fre
alue.
Cheers,
Rüdiger
On Wednesday, February 24, 2016 at 11:43:33 AM UTC+1, Konrad Malawski wrote:
Hey Rüdiger,
yeah those can definitely be used in all kinds of APIs.
The reason we have them mostly in Streams for now is because we could not break
compatibility in akka-actor for example.
Hi Tal,
thanks for pointing out it's not linked to in the docs around `ask`.
We have one and it's available in `akka.pattern.PatternsCS`,
so you can import statically from that object and it'll read nice (`ask(who,
what): COmpletionStage`) :-)
I'll add a note to the docs as well: https://github.
Happy hakking!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Lightbend
On 24 February 2016 at 16:53:43, Tal Pressman (kir...@gmail.com) wrote:
Hmm, not sure why I didn't find it myself. Sorry for the dumb question...
Thanks for the quick reply, though! ^_^
--
>> Read the docs: http:/
Yeah, for example if irrecoverable loss of system messages happens.
In general death watch on Actors using remoting can in failure scenarios (see
above) lead to a Quarantine.
Note that Quarantine is irrecoverable, unlike "Unreachable" which is used in
the Cluster.
Short answer: Use the Cluster –
Hi there,
I'm very glad you found it useful!
yeah, it's something on our radar to improve – specifically 2.0.3 should
redirect people to 2.4.2+.
It's somewhat of a special case as URL needs more change than just changing the
version in it,
so we didn't yet squeeze in the time to fix that...
If
A defer() just after the persistAll call should pretty much be what you
need, unless I missed something :)
On Feb 28, 2016 15:23, "Łukasz Gąsior" wrote:
> Hi,
>
> Is there a way to execute a handler when all events have been saved using
> persistAll?
> i.e. have (handler: Seq[A] => Unit) or even
Hi Oscar,
Akka definitely makes a lot of sense even just locally – Actors are also a
concurrency abstraction (much nicer to work with than threads).
One would need to know more about your project to say more however.
For example, while we have Actors, some things are better modeled as Akka
Strea
Hi there,
it's not a bug, it's about shutting down connections when no data is passed
through it.
It's fixed already and will be part of the 2.4.3 release:
https://github.com/akka/akka/pull/19915
Thanks for reporting!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Lightbend
On 4 March 2016 at 10:0
As mentioned by Guido,
we did loads of fixes in the cluster / sharding during the 2.3.x timeline,
you'll definitely want to upgrade to the latest 2.3.
Also, reminder that we made a specific effort to keep 2.3 and 2.4 binary
compatible (sic!) so you cna upgrade to the latest 2.4 as well!
One thin
We know the fine chaps over at Akka.NET a bit and I think you should give them
a try :-)
It's hard for me to say if the impl is nice and idiomatic for .NET, however as
you seem to have an Akka app migrating should be rather simple – they're very
much 1:1 with "Akka.JVM" as far as I remember.
--
Also... kind of surprising move: from JVM to .NET, I've seen more of the
opposite direction in the past.
I suspect it's not much about Akka itself but some organisational movements
or hiring things?
On Mon, Mar 7, 2016 at 11:01 PM, Konrad Malawski
wrote:
> We know the fine
Here's the ticket, you'd like to contribute these operations (it's pretty
easy to contribute, one can look at mapAsync and see how it differs from
map):
https://github.com/akka/akka/issues/18603
Thanks in advance if someone steps up to contribute!
On Tue, Mar 8, 2016 at 12:12 PM, Viktor Klang
wr
Correct, HTTPS Proxies are not supported yet, see ticket:
https://github.com/akka/akka/issues/16153
Sadly we're not sure when we'll get the chance to work on this yet.
For the time being you may want to try Play's WS library, though I'm not sure
if they support this feature hm...
(They're backed
Seems we might be missing some factory methods on the MediaTypes trait,
the scaladsl has methods for returning more specific types, such as
`applicationWithCharset` etc.
Would you please open a ticket about "feature parity of creating MediaTypes for
JavaDSL"?
Thanks in advance!
Please note tha
the quick answer. Fortunately it is only a small part of our code
that needs that. I will use Apache HttpClient for now, which does everything we
need.
Best regards,
Michael
On Tuesday, March 8, 2016 at 5:37:01 PM UTC+1, Konrad Malawski wrote:
Correct, HTTPS Proxies are not supported yet, see tick
(kami...@gmail.com) wrote:
OK, thanks, any hints how to work this around?
I ll create an issue.
On Tuesday, 8 March 2016 17:37:48 UTC+1, Konrad Malawski wrote:
Seems we might be missing some factory methods on the MediaTypes trait,
the scaladsl has methods for returning more specific types, su
Our http://resources.typesafe.com/monitoring/docs/ monitoring has seen an
internal release of supporting 2.4.2 already.
You can get access to it via getting a sub:
http://www.lightbend.com/services/expert-support
via this form: https://www.lightbend.com/company/contact
Hope this helps.
I'm not
501 - 600 of 1010 matches
Mail list logo
