Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 16:49
    Aaronontheweb synchronize #4159
  • 15:55
    IgorFedchenko synchronize #4157
  • 15:52
    yesh-nadella edited #4161
  • 15:50
    yesh-nadella opened #4161
  • 15:48
    IgorFedchenko commented #4157
  • 15:46
    IgorFedchenko commented #3786
  • 15:46
    IgorFedchenko synchronize #4160
  • 15:45
    IgorFedchenko synchronize #4160
  • 15:44
    IgorFedchenko opened #4160
  • 15:40
    Aaronontheweb commented #4157
  • 15:31
    IgorFedchenko commented #4157
  • 15:30
    IgorFedchenko synchronize #4157
  • 15:30
    IgorFedchenko commented #4157
  • 15:19
    IgorFedchenko commented #4157
  • 15:16
    IgorFedchenko commented #3786
  • 15:15
    IgorFedchenko edited #4159
  • 15:14
    IgorFedchenko opened #4159
  • 15:03
    IgorFedchenko synchronize #4158
  • 15:02
    IgorFedchenko commented #4158
  • 14:52
    IgorFedchenko commented #4158
Aaron Stannard
@Aaronontheweb
you'd be able to setup a chaos-monkey-esque scenario using the former
it's probabilistic, FYI
you set a packet loss percentage
or you can use a
blackhole setting
which essentially forces a disconnect
Joshua Garnett
@joshgarnett
Cool, any way to also do that for local akka messages?
Aaron Stannard
@Aaronontheweb
probably by writing a custom mailbox implementation
that would behave the same way
Joshua Garnett
@joshgarnett
Good idea
cool, we shall see how this goes
Trying to debug some non-deterministic behavior, it’s been fun
Aaron Stannard
@Aaronontheweb
have you heard of FsCheck?
Joshua Garnett
@joshgarnett
nope
Aaron Stannard
@Aaronontheweb
it's how I find a lot of heisenbugs in my code and we use it in a few places here in the Akka.NET test suite too
I need to finish the part 3 of that series one day
it uses property and model-based testing
found tons of weird edge cases in production Akka.NET code with it
Joshua Garnett
@joshgarnett
Nice
Aaron Stannard
@Aaronontheweb
like a scenario where restarting one actor three times in a row broke a big piece of functionality, a scenario I would have never thought to test
Andrew Young
@ayoung
@uatec was that directed to me?
still don't know why Proto.Actor exists. Can someone comment?
Bartosz Sypytkowski
@Horusiath
@ayoung you could ask this question on proto.actor channel. IMO it result of some of the Roger's thoughts on akka's actors, that couldn't be implemented in akka itself because of legacy reasons. Personally me (and probably many people in the core team) sympathize with at least some of those ideas - we talked about them even before birth of proto.actor.
Phil Sandler
@philsandler_twitter
Thanks @Aaronontheweb --makes sense.
chipdice
@chipdice
Is there something special I need to do in order to serialize an enum as part of a message? I'm using Hyperion and as soon as I add my enum to a message I send, I get an error. ERROR 2017-09-14 14:35:54,547 [25] TcpServerHandler - Error caught channel [::ffff:172.16.165.175]:9710->[::ffff:172.16.165.175]:64469
System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at DotNetty.Transport.Channels.Sockets.SocketChannelAsyncOperation.Validate()
at DotNetty.Transport.Channels.Sockets.AbstractSocketByteChannel.SocketByteChannelUnsafe.FinishRead(SocketChannelAsyncOperation operation)
DEBUG 2017-09-14 14:35:54,551 [25] EndpointWriter - Disassociated [akka.tcp://PMTActorSystem@chipd-pc2:9710] <- akka.tcp://PMTActorSystem@chipd-pc2:9560
WARN 2017-09-14 14:35:54,552 [25] ReliableDeliverySupervisor - Association with remote system akka.tcp://PMTActorSystem@chipd-pc2:9560 has failed; address is now gated for 5000 ms. Reason is: [Akka.Remote.EndpointDisassociatedException: Disassociated
at Akka.Remote.EndpointWriter.PublishAndThrow(Exception reason, LogLevel level, Boolean needToThrow)
at Akka.Remote.EndpointWriter.Unhandled(Object message)
at Akka.Actor.ReceiveActor.ExecutePartialMessageHandler(Object message, PartialAction`1 partialAction)
at Akka.Actor.ReceiveActor.OnReceive(Object message)
Saepul Ramdani
@blackclavus
Is there anyway to check current actor's behavior?
Stephen Newman
@goodisontoffee
@Aaronontheweb thank you for the Akka.Monitoring drop :)
Arsene
@Tochemey

Hello geeks, I am having an issue after updating my Akka packages:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Void Hyperion.SerializerOptions..ctor(Boolean, Boolean, System.Collections.Generic.IEnumerable`1<Hyperion.Surrogate>, System.Collections.Generic.IEnumerable`1<Hyperion.SerializerFactories.ValueSerializerFactory>, System.Collections.Generic.IEnumerable`1<System.Type>)'.
   at Akka.Serialization.HyperionSerializer..ctor(ExtendedActorSystem system, HyperionSerializerSettings settings)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, Object[] args)
   at Akka.Serialization.Serialization..ctor(ExtendedActorSystem system)
   at Akka.Actor.Internal.ActorSystemImpl..ctor(String name, Config config)
   at Akka.Actor.ActorSystem.Create(String name)

Please assist. This is my config is the app.config:

  <akka>
    <hocon>
      <![CDATA[
          akka 
          {
            loggers = ["Akka.Logger.NLog.NLogLogger, Akka.Logger.NLog"]
            # here we are configuring log levels
            stdout-loglevel = DEBUG
            loglevel = DEBUG
            log-config-on-start = off        
            actor 
            {                
                debug 
                {  
                      receive = on 
                      autoreceive = on
                      lifecycle = on
                      event-stream = on
                      unhandled = on
                }
                serializers {
                      hyperion = "Akka.Serialization.HyperionSerializer, Akka.Serialization.Hyperion"
                }
                serialization-bindings {
                  "System.Object" = hyperion
                }                
            }
          }
      ]]>
    </hocon>
  </akka>
Stephen Newman
@goodisontoffee
@Tochemey You need to update to the latest prerelease package for Akka.Serialization.Hyperion
Arsene
@Tochemey
Ok thanks man
I will give it a try
Arsene
@Tochemey
@goodisontoffee Thanks man. It works :smile:
Kevin McFarlane
@kevinmcfarlane
I notice that that the Akka.NET home page has some broken links in the "read more." Also the copyright is saying 2013-2016.
Aaron Stannard
@Aaronontheweb
@kevinmcfarlane would you mind logging an issue with some of those? we'll fix it
the copyright footer fix should be a breeze too
Kevin McFarlane
@kevinmcfarlane
Hi Aaron, I'll try and do so over the weekend. At work at the moment. :)
Michel van den Berg
@promontis
What to do when I have a coordinator actor that will deploy work to worker actors on a number of nodes and the number of worker actors is very high (say a million). The coordinator actor is persistent and has a million WorkerCreated events. Will this one coordinator actor be able to handle the creation of a million worker actors by reading the journal? Or will this take a long time? If so, how to speed this up?
Robert Stiff
@uatec
hey
https://getakka.net http cert appears to be wrong
getting an azure websites one
Gregorius Soedharmo
@Arkatufus
uh oh...
i'll let the other core team member know, thanks
Chris Ochs
@gamemachine
So long time user of akka but decided to give orleans a shot on my current game. I've noticed something very different at a core level, which is orleans is slow as hell. SOme of it is the serialization, but some of it appears to be that await is just slow. Does akka internally use some magic to make sending messages faster then a simple await?
on akka jvm as of around 2 years ago, the same basic logic I was pushing 50k messages second. Akka.net I didn't do as much testing, but it wasn't far behind at around the same cpu load. Orleans falls over at the same load, doesn't even get 20% of the way there
Ronny Carlansson
@lessismore1
Unable to find documention of HOCON. Need info about - akka.actor.ask-timeout. Pointers?
Bartosz Sypytkowski
@Horusiath
@lessismore1 akka.actor.ask-timeout was not originally part of JVM config, since in Scala you always have timeout as implicit parameter. We added it to allow people to set a global timeout on their Ask requests, so they don't need to pass timeouts each time. By default it's null (for backward compatibility story), but you can set it to any HOCON time value (i.e. 5s, 500ms etc.)
Ronny Carlansson
@lessismore1
Thanks for a quick reply! :) Working...
Bartosz Sypytkowski
@Horusiath
@gamemachine it's more the Orleans side - when you're calling grain methods, it's not just a simple await.
Ronny Carlansson
@lessismore1
Tried ImmutableSortedDictionary as actor state in a persistenceactor. Snapshots fails to load due to an requirement NewtonSoft have on immutables. Any hints?