by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 00:03
    Aaronontheweb commented #4434
  • May 27 23:41
    Zetanova commented #4434
  • May 27 22:57
    Zetanova commented #4434
  • May 27 22:34
    Aaronontheweb commented #4419
  • May 27 15:54
    Ralf1108 commented #4432
  • May 27 14:42
    Ralf1108 commented #4419
  • May 27 09:41
    Zetanova commented #4434
  • May 27 06:38
    dependabot-preview[bot] labeled #141
  • May 27 06:38
    dependabot-preview[bot] opened #141
  • May 27 06:38

    dependabot-preview[bot] on nuget

    Bump AkkaVersion from 1.4.6 to … (compare)

  • May 27 06:33

    dependabot-preview[bot] on nuget

    (compare)

  • May 27 06:33
    dependabot-preview[bot] closed #156
  • May 27 06:33
    dependabot-preview[bot] commented #156
  • May 27 06:33
    dependabot-preview[bot] labeled #157
  • May 27 06:33
    dependabot-preview[bot] opened #157
  • May 27 06:33

    dependabot-preview[bot] on nuget

    Bump AkkaVersion from 1.4.5 to … (compare)

  • May 27 01:23

    Aaronontheweb on dev

    added v1.4.8 placeholder for ni… (compare)

  • May 27 01:23

    Aaronontheweb on 1.4.7

    (compare)

  • May 27 01:21

    Aaronontheweb on master

    Added v1.4.7 placeholder for ni… fix: improve doc for persistenc… Bump Microsoft.Extensions.Depen… and 18 more (compare)

  • May 27 01:21
    Aaronontheweb closed #4444
Bartosz Sypytkowski
@Horusiath
@kevinmcfarlane if I'm right you're trying to check if ZipMessage has reached ZipActor, right?
If so, you need to know, that this is not what ExpectMsg is made for. What it's made for is testing if messages reach mailbox of the TestActor, not your custom actors
@chillitom we need reactive streams first ;)
Kevin McFarlane
@kevinmcfarlane
Bartosz Sypytkowski
@Horusiath
@kevinmcfarlane just like I said, you didn't quite understood what ExpectMsg is made for
don't test if message has reached an actor - if you do, you actually test the framework, not your code ;)
Bartosz Sypytkowski
@Horusiath
instead test behavior of actor itself - activate it's behavior trough message and assert side effects or messages, it generated in return. This is what ExpectMsg was made for
Amon-Ra Mackie
@nevaenuf
Got a question concerning supervisor strategies. Does anyone know how to get access to the message that causes a failure without creating a wrapper exception and trapping the message?
Bartosz Sypytkowski
@Horusiath
@nevaenuf you probably can't unless you pack it inside message itself. Parent actor doesn't need to be aware of every message coming to it's children. What do you need it for?
Amon-Ra Mackie
@nevaenuf
@Horusiath the message contains information that I use for logging when a child actor fails. Also, the child actor represents a unit of work that I need to report on to give the user an opportunity to restart if they so desire. I could trap the exception, tell to sender, and throw as well, but didn't know if that's the best strategy.
Aaron Stannard
@Aaronontheweb
@nevaenuf hmm... you could design a custom SupervisionStrategy that reads state from the exception object, and you could include the message that triggered the exception as part of that state
Bartosz Sypytkowski
@Horusiath
In general supervision strategies are used solely to tell child, what to do.
You can log error on actor level itself. When it comes to restarts, you can order actor to send back some dedicated failure message in PreRestart or PostStop method.
Amon-Ra Mackie
@nevaenuf
@Horusiath, that seems to conflict with the advice @Aaronontheweb just gave. Should we not be logging or performing
Bartosz Sypytkowski
@Horusiath
i.e. PreRestart has access to both exception and message
Amon-Ra Mackie
@nevaenuf
@Horusiath , rat's i just hit enter instead...
Cool. That's what I wanted to know. So if I wanted to stop the child, I should send a poison pill to the child in the PreRestart after logging the exception?
Bartosz Sypytkowski
@Horusiath
I shared my opinion ;) usually there is more than one way to solve the problem, and it's up to you to figure out what is working
Amon-Ra Mackie
@nevaenuf
Yeah, I'm new to this system, so I'm trying to go for best practices. But I appreciate the help!
Bartosz Sypytkowski
@Horusiath
PreRestart is called when child will be restarted, but not stopped.
Amon-Ra Mackie
@nevaenuf
@Horusiath @Aaronontheweb Thanks guys. I'm going with the simple approach and packing the message inside an exception. Seems the easiest way and more importantly, the most expected way to use the framework for a bunch of newbies.
Darren Ford
@4deeptech
@trbngr I'm interested in your ARM templates for the EventStore cluster. Do you have those out somewhere?
Bartosz Sypytkowski
@Horusiath
I feel, that I need to show off my new version of API for Akkling (my fork of Akka F# API, that adds new style and compile type checking for messages passed through actor refs) - examples are here and they look pretty sweet. I'm esspecially proud of totally new API for persistence.
Weston
@ronnyek
I feel like f# could have been better with a better syntax
Aaron Stannard
@Aaronontheweb
off-topic - anyone know somebody at JetBrains? Spent 10 hours today re-imaging our build agents over and over again when this was the issue the entire time: https://devnet.jetbrains.com/thread/473684
can't run more than 1 cloud agent at a time with VS2015 until that issue gets fixed - looks like the agent is reading the build server ID out of the build image and not the actual instance metadata
Tom Rathbone
@chillitom
@Horusiath Akkling examples look good, being a fork can I assume it implements all the features of the existing F# api?
Bartosz Sypytkowski
@Horusiath
@chillitom I'm not sure if all of them were necessary. In general it should allow for everything, that original F# API allowed (at least in Akka.NET context), but it's done differently in many cases. After my yesterday changes next version of Akkling won't be API-compatible with Akka.FSharp
in case of persistence, Akkling.Persistence it's both a lot simpler and allows to do a lot more than original Akka.FSharp.Persistence
Tom Rathbone
@chillitom
How about calling it Fakka? ;-)
Bartosz Sypytkowski
@Horusiath
maybe Fakkap?
:P
Tom Rathbone
@chillitom
Can anyone tell me how I run the Postgres persistence adaptor's spec tests?
Bartosz Sypytkowski
@Horusiath
tbh naming is not so important, I've created this to experiment on F# API, once it's get proven, complete and stable I hope to incorporate it into new version of Akka.FSharp
you'll need a postgres installed on your local machine with database and credentials used by specs
Tom Rathbone
@chillitom
should an xunit running pick up the tests or do i need something else
would be great to see your changes merged back to master
Arjen Smits
@Danthar

@Horusiath > maybe Fakkap?

Nearly choked on my tea there.

Bartosz Sypytkowski
@Horusiath
@chillitom I was using Resharper test runner for basically all plugins that doesn't need a cluster multinode test runner, it's fine
however if I remember correctly, there is a problem with resharper that it may "leak out" some test from test visual tree display if you'll try to step into particular test from that UI control directly
Tom Rathbone
@chillitom
Hmm odd, R# not finding anything, all I see are two classes that extend JournalSpec and SnapshotStoreSpec
Tom Rathbone
@chillitom
Ahh NCrunch can see them, xunit must still be plugin or something for r#
Tom Rathbone
@chillitom
Just created this as couldn't find an existing implementation: https://github.com/chillitom/Akka.Persistence.MySql
Kevin McFarlane
@kevinmcfarlane
:point_up: November 16, 2015 7:20 PM @Horusiath, with your assistance and AndrewS I have updated my SO post with my solution.
Tom Rathbone
@chillitom
Anyone seen this issue before with Akka.FSharp...
System.MissingMethodException : Method not found: 'Void Nessos.FsPickler.BinarySerializer..ctor(Microsoft.FSharp.Core.FSharpOption1<Boolean>, Microsoft.FSharp.Core.FSharpOption1<Nessos.FsPickler.ITypeNameConverter>)'.
at Akka.FSharp.Serialization.ExprSerializer..ctor(ExtendedActorSystem system)
at Akka.FSharp.Serialization.exprSerializationSupport(ActorSystem system)
I'm using 1.0.4 for Akka/Akka.FSharp and have tried versions 1.2.21 and 1.5.2 of FsPickler
Bartosz Sypytkowski
@Horusiath
@chillitom have you set assembly bindings for FsPickler 1.2 in your app.config?
Joshua Benjamin
@annymsMthd
@Aaronontheweb do the build agents require VS because of the MSTests?
Tom Rathbone
@chillitom
@Horusiath that did the trick, thanks for that