Yeah, thanks Samuel for linking to the issue.
Interested parties please watch that issue and PR :)
On Tue, Mar 15, 2016 at 9:51 AM, Samuel Tardieu wrote:
> I think this is a bug: https://github.com/akka/akka/issues/20032
>
>
> Le mar. 15 mars 2016 à 03:57, Sam Smoot
I think this is a bug: https://github.com/akka/akka/issues/20032
Le mar. 15 mars 2016 à 03:57, Sam Smoot a écrit :
> That fixed it! I can't thank you enough!
>
>
> On Monday, March 14, 2016 at 5:43:05 PM UTC-5, Samuel Tardieu wrote:
>
>> Could it be that since you define an
Ah. I didn't realize self was a val. I always assumed it was just a
delegating method to context.self. Thanks for the tip.
For posterity: I was trying to provide a local val the closure I was using
for my Future callback could capture so that if the underlying ActorRef
returned by context.self
That fixed it! I can't thank you enough!
On Monday, March 14, 2016 at 5:43:05 PM UTC-5, Samuel Tardieu wrote:
>
> Could it be that since you define an implicit Materializer in your actor
> which is tied to the implicit ActorRefFactory (which would be context
> inside the actor), it is the one
Could it be that since you define an implicit Materializer in your actor
which is tied to the implicit ActorRefFactory (which would be context
inside the actor), it is the one used for singleRequest which requires an
implicit Materializer? Can you try defining your Materializer as
As a side node: self is already defined as context.self in Actor, you can
use that directly.
Le lun. 14 mars 2016 à 18:36, Sam Smoot a écrit :
> So if you look at the example in the docs:
>