issue with FAKE?
Running build failed.
Error:
System.Exception: Start of process failed. Cannot start process because a file name has not been provided.
at Fake.ProcessHelper.ExecProcessWithLambdas@76-16.Invoke(String message) in C:\code\fake\src\app\FakeLib\ProcessHelp
er.fs:line 76
at Fake.ProcessHelper.ExecProcessWithLambdas(FSharpFunc`2 configProcessStartInfoF, TimeSpan timeOut, Boolean silent,
FSharpFunc`2 errorF, FSharpFunc`2 messageF) in C:\code\fake\src\app\FakeLib\ProcessHelper.fs:line 76
at Fake.MSTest.MSTest(FSharpFunc`2 setParams, IEnumerable`1 assemblies) in C:\code\fake\src\app\FakeLib\UnitTest\MSTe
st.fs:line 100
at FSI_0001.Build.clo@209-14.Invoke(Unit _arg9) in D:\Repositories\olympus\akka.net\build.fsx:line 218
at Fake.TargetHelper.runSingleTarget(TargetTemplate`1 target) in C:\code\fake\src\app\FakeLib\TargetHelper.fs:line 48
3
symbolic link FTW
And the next one: If the process-actor is with a router (smallest inbox) it would need to host the real process-actor as a child, so that the process-actor can hold new commands from the router back until the child terminates. looks very complicated ... schould it be? The hole router would be then pointless. Until the process-actor would lock itself over the time of the processing and communication to the AR's and Caller (Cancel) over a child actor.
@Zetanova
- You could just store actors, which you'll send update message to, in separate struct like Set. Then wait for them to respond, and take of all responders from the set. Once set is empty or timeout will occur (using SetReceiveTimeout) you could send completion/failure message.
- Probably router is not a good choice in this scenario.
hi. i have the next section in my HOCON config:
dedicated-dispatcher {
type = PinnedDispatcher
throughput = 100
}this line
var userApp = _actorSystem.ActorOf(Props.Create<UserAppActor>().WithDispatcher("dedicated-dispatcher"), "user-app");throws an exception "Akka.Configuration.ConfigurationException: Dispatcher [dedicated-dispatcher] not configured for path ..." though the documentation says that a dispatcher can be set using code here http://getakka.net/docs/working-with-actors/Dispatchers#configuring-dispatchers
so such a behavior is a bug?
@Horusiath i am basicly getting data from a external service and looking it up on the read-model. If found i send to the AR an updateCommand, if not i send to the AR an addCommand. The AR's on UpdateEvent would Tell the State back. this State i need to send back to the caller of the process. This task can run over 30min
its getting somehow complicated :(
Whoops - typing on mobile
It's just to illustrate a way to implement some sort of consensus model using messages
I don't see, where TaskScheduler should be used.
@Horusiath What is the best way to delay the delivery of a message ? ScheduleTellOnce ? I have two actors A and B, a tells B to update, B send back it state, A compute the next time it should update and delay the update message in order to have a constant intervall between updates
but remember that schedulers have limited resolution, as they work in intervals themselfs (by default it's around 10ms)
@andreichuk my guess is that string, you've provided in dispatcher is invalid, but maybe it's a bug. Could you write an issue on github and describe your case?
there are some examples in the docs but they are not full so it's not clear where exactly put dispatcher configuration there
This is a critical point of my system
I know that you can configure the interval, but I'm not sure, how will it behave in intervals lower than 10ms. I don't think, it was designed for high time sensitivity, but for 60 frames/sec it should be sufficient. However if I were you, I would check if it fits your needs
don't be driven by the belief. If you won't measure and stay with built-in scheduler, it may give you some performance problems later. But if it turns out it's sufficient, but you've moved this part outside an actor system, then you may end with unnecessarily complicated solution
@Horusiath the process to download the data can take 30min, its an import from the external system. Because this process relays on the read-model for index lookup, maybe should it just be outside? the AR have near the same ImportCommand. It just query the external service for the data and generates a Created+Updated Event. On CreateCommand the AR is creating the external account first and generates the Created Event.
some race conditions
when i push messages to the AR
how to force the creation of the snapshot extension?