These are chat archives for akkadotnet/akka.net

21st
Mar 2015
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:09
is there any way to override actor system settings after it's created?
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:32
I've got a lot freakin problems with persistence specs, when I run them one by one, it's all ok, when I run then all at once, a random failures occurs almost everytime
Roger Johansson
@rogeralsing
Mar 21 2015 13:32
Depends on what settings you want to change. the core settings are parsed only once at start up, but you can inject top level fallbacks (you do that in f# module, right?)
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:34
@rogeralsing nope, just for some specs (I've noticed that one of my tests using TestLatches was hanging when message serialization was turned on)
but eventually I just moved it to separate spec class
Roger Johansson
@rogeralsing
Mar 21 2015 13:34
I've seen a similar problem before, back then, it was that some static resources, like NoRouter or DefaultDeploy or whatver, was overwritten by the serializer .. e.g. some primitives took a static resource as an input argument, then the serializer overwrote the properties of the primitive, which was backed by the static resource, and tada , the static resource was corrupted
could that be a similar problem here?
e.g. public Props() : this(Some.Static.Resource) {} then when the deserializer tried to deserialize an object with such ctor, the injected resource would be corrupted
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:36
I know that test latch uses System.Threading.CountdownEvent so I supose it may be not safe to try to serialize/deserialize it
Roger Johansson
@rogeralsing
Mar 21 2015 13:37
were you passing a testlatch object as a message?
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:37
I have to for test verification ;)
Roger Johansson
@rogeralsing
Mar 21 2015 13:38
and if so, shouldnt that be marked with the INoSerializationNeeded or whatever the name
NoSerializationVerificationNeeded
that will ofc not help if the testlatch is part of a bigger message, but if it is the root, that would make it bypass serialization in inproc systems
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:41
it worked, I didn't know about that interface
Roger Johansson
@rogeralsing
Mar 21 2015 13:42
its in the scala version too
neat :) so for persistence, we just need to start making providers? and follow typesafes lead on how to take it out of beta (?)
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:45
not all of exisiting tests are passing yet (6 out of 82 total are marked to be skipped, I need to fix them probably)
beside that, I'm currently during writing some tutorial about how to write custom persistence plugins
Roger Johansson
@rogeralsing
Mar 21 2015 13:46
So what probiders do you think are the most important ones? SqlServer, different Azure storages, flat file?
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:46
also I'm in midway of creating Akka.Persistence.SqlServer plugin
Roger Johansson
@rogeralsing
Mar 21 2015 13:46
:+1:
Bartosz Sypytkowski
@Horusiath
Mar 21 2015 13:48
those two definitely yes, snapshot store for local file system already exists (I've rewritten it <not pushed yet>). I don't know if some other providers should be included to akka.net core repository
but I think, that @Aaronontheweb or @jcwrequests may want to try to implement Cassandra plugins for Akka.Persistence
I also hope, that when it will be ready to drop -Pre flag, RavenDB and EventStore creators will want to integrate their services too
jcwrequests
@jcwrequests
Mar 21 2015 18:13
@horusiath
jcwrequests
@jcwrequests
Mar 21 2015 20:43
@horusiath is your SQL code on your Akka fork? I think it would be a good idea to write them for Cassandra, mongo, postgres and maybe foundation db. I think that the focus should be on the high write throughput DBs. @arronontheweb might have some during opinions about ravendb 😊.