Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 20:57
    IgorFedchenko commented #4085
  • 20:32
    IgorFedchenko commented #4085
  • 20:01
    IgorFedchenko commented #4085
  • 19:55
    IgorFedchenko commented #4085
  • 16:22
    Aaronontheweb labeled #3997
  • 16:22
    Aaronontheweb closed #3997
  • 16:20
    IgorFedchenko commented #3997
  • 16:08
    IgorFedchenko commented #4085
  • 15:50
    Aaronontheweb assigned #4085
  • 15:50
    Aaronontheweb labeled #4085
  • 15:50
    Aaronontheweb labeled #4085
  • 15:49
    Aaronontheweb closed #4032
  • 14:58
    IgorFedchenko commented #4032
  • 14:57
    IgorFedchenko opened #4085
  • Dec 05 17:21
    Aaronontheweb synchronize #4079
  • Dec 05 17:20
    Aaronontheweb labeled #4084
  • Dec 05 17:20
    Aaronontheweb labeled #4084
  • Dec 05 17:20
    Aaronontheweb milestoned #4084
  • Dec 05 17:20

    Aaronontheweb on dev

    Remove string interpolation fro… (compare)

  • Dec 05 17:20
    Aaronontheweb closed #4084
Arjen Smits
@Danthar
you could put it in an appsetting value in your config
and read it from there
Bartosz Sypytkowski
@Horusiath
when you're creating actor system by ActorSystem.Create("sys") this is actually a shorter form of ActorSystem.Create("sys", ConfigurationFactory.Load()) which loads config from web.config
Peter Bergman
@peter-bannerflow

I have some issues with TestKit and xunit console runner. When I run my tests through VS they pass fine, but when using the console runner (as my CI tool does) they fail. The tests cases are basically doing the following:

  1. Create an actor, 2. Send it a message, 3. Expect another message back to the TestActor.
    When running the tests through the console, I observe that the message sent in step 2 is unhandeled:

[WARNING][2016-10-07 13:29:56][Thread 0005][akka://test/user/$c] Unhandled message from [akka://test/user/testActor1#360950702]: Common.Models.Messages.Worker.Parse

And that basically causes the test to fail. Would that indicate that the message is sent before the actor under test has been created?

Arjen Smits
@Danthar
does it always fail ? or intermittenly ?
Peter Bergman
@peter-bannerflow
Actually, never mind, I think it is a bug in my application code... :(
Arjen Smits
@Danthar
ok
Peter Bergman
@peter-bannerflow
Any way I could do a test with an assert like ExpectOneMsg<Foo>()?
To check that I don't receive multiple instances of the Foo message
Marc Piechura
@marcpiechura
@peter-bannerflow ExpectMsg + ExpectNoMsg or ReceiveWithin and then check the result
Peter Bergman
@peter-bannerflow
Ah I see, that could work, thanks
Andrew Young
@ayoung
@Horusiath let me try to clarify a bit. my actor hierarchy is a bit like this hashPool -> process actors -> broadcastGroup. The hash pool at the top is what complicates things because it remotely deploys the process actors. that is what makes the actor selection so difficult for me to configure for the broadcast group.
Sean Farrow
@SeanFarrow
Has anyone done anything using redis, specifically, subscribing to a channel and receiving messages in actors. I'm trying to communicate between a JavaScript application and a backend written using Akka.net actors. Any help appreciated.
Bartosz Sypytkowski
@Horusiath
@ayoung to be honest I've never seen real use case scenario for consistent hash pool and 90% of the people trying it was actually misused it
Arjen Smits
@Danthar
@SeanFarrow I have used the stackexchange redis client. Could not get the connection multiplexer to work properly inside an actor.
Dont know why, the multiplexer just didn't like it.
But i have not used channels. What i do though is setup the connection outside of an actor, and pass it in as a reference to an actor.
But what you can do is receive messages from your channel, and then send them into your actor system via an IActorRef
Does that help ?
Sean Farrow
@SeanFarrow
@danthar, possibly I'll take a look. I was hoping to use Akka.Streams, but it seems that client won't allow me to, or will certainly have issues. I will have a lot of channels, So I need to work out whether one actor will do the trick or multiple actors are needed. The actors are sending back to a SocketIO node api.
Peter Bergman
@peter-bannerflow
@Danthar I am also using the stackexchange redis client and it seem to work fine. I create a static ConnectionMultiplexer reference in my main service class where I boot up my actor system, then I do GetDatabase() calls on that reference from inside my actors
Marc Piechura
@marcpiechura
@SeanFarrow out of curiosity, why aren't you allowed to use streams?
Sean Farrow
@SeanFarrow

+

All Conversations

Activate or click this element to toggle the profile menu

Search

Favourites

People

akkadotnet

Home

Billing

Get Gitter Apps

Allow Private Repo Access

Sign Out

Add a room

akka.net

Leave

Hide

Your Suggestions

SuaveIO/suave

aurelia/Discuss

akka/akka

mono/mono

dotnet/corefx

dotnet/coreclr

akka-bootcamp

helios-io/helios

IdentityServer3

visualfsharp

TypeScript

Rx.NET

Your Organisations

Twitterizer

I'm not saying I'm not allowed to use streams, the way the StackExchange Redis subscription system works doesn't lend itself to doing so though!

Marc Piechura
@marcpiechura
Ahhh :) I thought client = customer ;)
Sean Farrow
@SeanFarrow

@Silv3rcircl3 It's nots that simple! I think I've fiund a solution, when I validate it, I'll let you know--you never know, I might release it as open source!

+

All Conversations

Activate or click this element to toggle the profile menu

Search

Favourites

People

akkadotnet

Home

Billing

Get Gitter Apps

Allow Private Repo Access

Sign Out

Add a room

akka.net

Leave

Hide

Your Suggestions

SuaveIO/suave

aurelia/Discuss

akka/akka

mono/mono

dotnet/corefx

dotnet/coreclr

akka-bootcamp

helios-io/helios

IdentityServer3

visualfsharp

TypeScript

Rx.NET

Your Organisations

Twitterizer

It's not that somple. I think I've got a solution though, when I find one, I'll let you know!

Marc Piechura
@marcpiechura
@seanfarrow let me know if you need some help. Also maybe my Azure adapter can give you some inspiration, don't know how Redis works but maybe it helps https://github.com/Silv3rcircl3/Akka.Streams.Azure
Aaron Stannard
@Aaronontheweb
boy, I've missed a lot of messages in here
vacation and doing remote work :p
In the UK at the moment; should be here through the end of the next week
but will go through all of this once I'm back
probably going to do a small point release soon with some minor Streams bug fixes, fixes for the priority mailbox, and others
also thinking about sending in a PR to skip some of the specs we know to be broken like the ClusterClient specs
no point in just re-running stuff repeatedly when the thing under test doesn't work
there's some specs, like the ActorsLeakSpec in Akka.Remote, that are just super complicated and can time out when things get busy... which makes me think maybe I should $$$ and increase the size of our VMs
Peter Bergman
@peter-bannerflow
When running an Akka.Cluster, is there any way for an actor in an actor system that has joined the cluster to get information about the number of nodes that joined the cluster with a specific role? I am just interested in the count nothing more than that
Aaron Stannard
@Aaronontheweb
@peter-bannerflow yep, Cluster.State will have that data
basically just iterate over all members and select them by their role
Peter Bergman
@peter-bannerflow
Nice, perfect :)
Vagif Abilov
@object
I am checking out a WebCrawler sample updated by @Aaronontheweb, the akka-streams branch revised to use Akka.Streams. Am I correct that the sample is not finished and quite a lot code may be removed? Right now it looks like Stream implementation is added on the top of the old code, so it's a hybrid sample supporting both plain actors and Akka streams. Is this so?
Marc Piechura
@marcpiechura
@object akka streams is bound to a local actor system so you need plain actors with clustering to distribute the work across nodes
Problem is that the reactive stream protocol works with demand that is send upstream and needs full deliver guarantees because otherwise the stream would deadlock
Vagif Abilov
@object
@Silv3rcircl3 yes, but I see that DownloadCoordinator code just increased by 50 lines and a new case (StreamCompleteTick). Shouldn't the newly introduced workflow graph replace some of low-level actor arrangements?
Marc Piechura
@marcpiechura
Don't know :) haven't looked at the code and don't know what is planed. Thought your question is more related to the fact that plain actors are used for the distributed work
Cc @Aaronontheweb
Vagif Abilov
@object
I understand that the implementation of Akka streams require materializer to be backed by actual actors, I am just trying to make sense of the example and reacted on the fact that it kept more or less the same complexity plus added stream flow.
Perhaps @Aaronontheweb can clarify it that example needs some cleanup.
Marc Piechura
@marcpiechura
That's not 100% correct, one feature of akka streams is that you can create your own materializer that doesn't need to use actors under the hood, for example on the jvm they released a new Gearpump materializer that can distribute a stream
Vagif Abilov
@object
@Silv3rcircl3 and when it comes to actor system requirement, what if the flow contains a trivial functional transformation, e.g. some arithmetic or string processing function, does it still require an actor for this?
Oh you already answered my next question, but can I combine actors and non-actors in the same flow?
Marc Piechura
@marcpiechura
Not sure I understand your question correctly, if for example you use a where + select these two stages would run in the same actor, this feature is called "Fusing", the stages are fused together, into a single actor, if they doesn't have async boundaries