Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 07:34
    Kenji-Tanaka commented #3887
  • 00:55
    Horusiath labeled #4026
  • 00:55
    Horusiath labeled #4026
  • Nov 11 20:30
    IgorFedchenko commented #4031
  • Nov 11 20:24
    IgorFedchenko commented #4031
  • Nov 11 20:18
    IgorFedchenko commented #4031
  • Nov 11 20:15
    IgorFedchenko commented #4031
  • Nov 11 18:06
    AndrewBoklashko commented #4026
  • Nov 11 16:01
    IgorFedchenko edited #4031
  • Nov 11 15:59
    IgorFedchenko opened #4031
  • Nov 11 14:59
    ismaelhamed commented #4026
  • Nov 11 09:39

    dependabot-preview[bot] on nuget

    (compare)

  • Nov 11 09:39
    dependabot-preview[bot] closed #4010
  • Nov 11 09:39
    dependabot-preview[bot] commented #4010
  • Nov 11 09:39
    dependabot-preview[bot] labeled #4030
  • Nov 11 09:39
    dependabot-preview[bot] opened #4030
  • Nov 11 09:39

    dependabot-preview[bot] on nuget

    Bump Newtonsoft.Json from 9.0.1… (compare)

  • Nov 11 09:39
    dependabot-preview[bot] labeled #4029
  • Nov 11 09:39
    dependabot-preview[bot] opened #4029
  • Nov 11 09:39

    dependabot-preview[bot] on nuget

    Bump ApprovalTests from 3.0.10 … (compare)

Bartosz Sypytkowski
@Horusiath
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
@horusiath
jcwrequests
@jcwrequests
@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 😊.
Bartosz Sypytkowski
@Horusiath
@jcwrequests if you want to start, my sqlserver fork is not what you want (at least for now). Right now I'm hardening Akka.Persistence.Tests (they are randomly failing right now, mostly due to timeouts) and making an Akka.Persistence.TestKit to work easier with. If everything goes right, they could be released soon and then I'll prepare tutorial about how to start persistence plugin development - right now I already have sample code, but it's not commented.
Natan Vivo
@nvivo
@all, general question: in which cases Akka doesn't own the threads it uses for actors? And are these scenarios recommended for production or just for testing?
Roger Johansson
@rogeralsing
By default we execute on the threadpool, so we don't own those threads.. we can also execute on the GUI thread with the synchronization context dispatcher if you want an actor that updates GUI elements. we dont own that thread either... then we have cases like the new threadpool, that can be used to give some actors a higher priority than the others, those threads are owned by whatever threadpool we use under the hood, but yes you could consider those owned threads I guess.. so we can execute ontop of whatever the current dispatcher decides to run the work on
but in short, akka never does anything to the threads, it just executes the mailbox run on whatever scheduling mechanism is there
Natan Vivo
@nvivo
@rogeralsing got it. thanks!
jcwrequests
@jcwrequests
@Horusiath Got it.
Stefan Sedich
@stefansedich
When using PipeTo and an exception is raised in the Task is it possible to get that to propogate up to an unhandled actor exception so that it goes to supervision?
Stefan Sedich
@stefansedich
@Aaronontheweb answered the above for me, it was too late in the day and I was derping a bit.
I do have a question for the group though on how you would handle supervision in this scenario: https://gist.github.com/stefansedich/0c5e1d2ac431eccd9fed
In this scenario say DoStuff failed, I would want to restart the child, but to do that I would need to execute the Start message again to reset the internal state back to a starting point before kicking off again, what are the best ways to achieve this kind of thing?
My current solution is to pass a message to the parent, but I end up implementing my own retry and not taking advantage of the Supervisor strategy.
Roger Johansson
@rogeralsing
And I assume that Start carries information that is owned by someone else, e.g. the Parent here? so the parent have to be the one passing it?
Stefan Sedich
@stefansedich
yeah
sorry if the example is a bit shitty :)
the child actually notifies the parent of the change and parent keeps track of state, so it it has to restart parent would need to pass down the current value.
It is a position in a stream basically.
Roger Johansson
@rogeralsing
The actor logging solves this by passing back a message to the parent notifying that it is ready to work.. so in the ChildActor ctor, you could add a "Parent.Tell(new IAmReadyToStart())" kind of message, or is that what you are already doing?
when parent receives the IAmREadyToWork, it can pass the Start message back to the child
Stefan Sedich
@stefansedich
yeah that happens, the issue is how does supervision handle when DoWork fails and the parent has to pass a new Start after the child restarts.
Roger Johansson
@rogeralsing
the child will send a new IAmReadyToWork to the parent.. if you place that in the ctor
as the child actor will be recreated if you use Restart
Stefan Sedich
@stefansedich
so basically bypass supervision then?
Roger Johansson
@rogeralsing
no
Stefan Sedich
@stefansedich
oh right yep sorry
Roger Johansson
@rogeralsing
the ctor is always called on the restarting actor. so you can place parent notifications in there
Stefan Sedich
@stefansedich
yeah so the trick is let the child ask for work
never have the parent start it off
Thanks @rogeralsing that works a treat as usual there is a simple solution!
Stefan Sedich
@stefansedich
final thing on that @rogeralsing to fail the parent if the child terminates do you just watch it and listen to Terminated?
Once that happens I know the child is good and dead and it is time to give up, I would only want this on errors though not normal shutdown.
Raymen Scholten
@raymens
Does the Scheduler expose a list of scheduled items? Or is there some other way to 'deschedule' a task?
Roger Johansson
@rogeralsing
In the 0.8 version, you can schedule using a cancellationtoken. You can use that to cancel the task
In the new dev branch, the scheduler returns an ICancellable
Raymen Scholten
@raymens
Allright, thanks.
Natan Vivo
@nvivo
I'm getting an error on config loading where double quotes work, but single quotes gives an error. Shouldn't both work the same?
Natan Vivo
@nvivo

this works:

ConfigurationFactory.ParseString(@"akka { loggers = [""CustomLogger, Assembly""] }")

but this:

ConfigurationFactory.ParseString(@"akka { loggers = ['CustomLogger, Assembly'] }")

fails with "Logger specified in config cannot be found: "'CustomLogger, Assembly".

Roger Johansson
@rogeralsing
Ill have a look at it, could be a parser bug inside array
Roger Johansson
@rogeralsing
@nvivo hehe single quotes are not part of neither the json nor hocon spec.. so 'CustomLogger will be parsed as what hocon calls an unquoted string
agree that it would be useful, but I guess we should stick to the specs
Bartosz Sypytkowski
@Horusiath
when I run persistence tests (all at once) I've got random timeout exceptions all the time. ofc when I try to run them one by one to check, everything is ok
Roger Johansson
@rogeralsing
I came to think of that turbo button we had back in the 286/386 days :)
What if you run a subset of test? Maybe there are some specific tests that mess things up for others?
Bartosz Sypytkowski
@Horusiath
any domain subset of Akka.Persistence.Tests also cause this, only when I run them one by one, they pass
Roger Johansson
@rogeralsing
Even if two by two?
Possibly the threadpool is saturated, but that shouldnt be visible with a few tests at a time
Stefan Sedich
@stefansedich
should hostname casing matter? If I try use akka.tcp://import@foo:9998/user/foo
and my helios tcp hostname is FOO