Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 11:49
    IgorFedchenko commented #4085
  • 10:31
    IgorFedchenko commented #4085
  • 08:36
    IgorFedchenko commented #4085
  • Dec 06 20:57
    IgorFedchenko commented #4085
  • Dec 06 20:32
    IgorFedchenko commented #4085
  • Dec 06 20:01
    IgorFedchenko commented #4085
  • Dec 06 19:55
    IgorFedchenko commented #4085
  • Dec 06 16:22
    Aaronontheweb labeled #3997
  • Dec 06 16:22
    Aaronontheweb closed #3997
  • Dec 06 16:20
    IgorFedchenko commented #3997
  • Dec 06 16:08
    IgorFedchenko commented #4085
  • Dec 06 15:50
    Aaronontheweb assigned #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:49
    Aaronontheweb closed #4032
  • Dec 06 14:58
    IgorFedchenko commented #4032
  • Dec 06 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
Kris Schepers
@schepersk
would like to update the cluster out of beta asap :-)
Arjen Smits
@Danthar
i can imagine
1.1.1 is alot better then 1.08
Kris Schepers
@schepersk
so they say :P
Arjen Smits
@Danthar
@Aaronontheweb did an insane amount of work
Marc Piechura
@marcpiechura
replace me with @Horusiath about the sql-common question ;)
Arjen Smits
@Danthar
ah ok
Marc Piechura
@marcpiechura
have no idea too
Arjen Smits
@Danthar
:D
haven't seen @Horusiath around for a while, so no idea how up to date he is ^^
but our main blocker for akka persistence are the CI build images
the core team is currently working to resolve that by moving to docker images which we can host on an azure environment
that eliminates @Aaronontheweb as the bottleneck since he would be the person to normally build the build-agent images
This will really help in making it easier for contributors to help in keeping the persistence plugins up to date, and even introduce new integrations
So these are some of the steps we are taking to improve the speed at which we can keep the persistence plugins updated
Kris Schepers
@schepersk
awesome!
Arjen Smits
@Danthar
@slc if you can post your configs in a gist, i can take a look
slc
@slc
Will do
Arjen Smits
@Danthar
(or upload the solution somewhere)
slc
@slc
https://gist.github.com/slc/866aa2af1026ac70bd24bae872860734
solution upload is tricky for IP reasons
thats the two configs
super simple configs AFAIK
Arjen Smits
@Danthar
hmm, could you try adding the public-hostname = "127.0.0.1" to the helios.tcp segment
slc
@slc
will do now...
Ralf
@Ralf1108
hi all, I checked out the new Akka.net Streams feature and I think its very goog. One questions was left open. If I create a processing flow how can I distribute it across different machines. Are there any examples how to start?
Arjen Smits
@Danthar
not sure if its still needed.
slc
@slc
public-hostname = "127.0.0.1" Added.
No change. Still errors.
do I need to configure IIS Express in any special way?
The weird thing is that I can send the message from the web actor to the service actor with no problems
Marc Piechura
@marcpiechura
@Ralf1108 that's not possible out of the box. But what you can do is to have an actor that distributes "job" messages to different machines and have a stream on every machine.
Arjen Smits
@Danthar
@slc no.
slc
@slc
I just cant Tell() back to the web actor from the service actor
James Farrer
@jamesfarrer
thanks @cgstevens and @qwoz . most helpful
Arjen Smits
@Danthar
@slc what if you reduce it to its bare minimum. So send a message containing nothing more then a string, and use Sender.Tell to echo it back
slc
@slc
I think I'm going to have to
Arjen Smits
@Danthar
that would eliminate possible serialization issues
slc
@slc
I was wondering if that was the case
Marc Piechura
@marcpiechura
@Ralf1108 here is some documentation about this topic http://getakka.net/docs/streams/integration#integrating-with-actors also @Aaronontheweb is currently rewriting the webcrawler sample to implement exactly the behavior you described
slc
@slc
I will try sending a string instead, or perhaps a bool
Ricky Blankenaufulland
@ZoolWay
@slc I have not followed the whole conversation but because I falled into the trap this week when messages have been swallowed: You are not creating one of the actors in an async method?
slc
@slc
nope, all syncronous
Ricky Blankenaufulland
@ZoolWay
ok
then check for the string/bool
slc
@slc
no async/await anywhere
yup, just about to try that
cannot Tell(true) either
:(
I guess that somewhat rules out serialisation/deserialisation issues
Im going to pull out an example from my solution and see if I can replicate in isolation