-
This is likely a supervision issue, but in case it's not I'm starting here first... and either way, this affects usage of `Celluloid::Actor[]` ... working on reproductions, but not seeing consistent f…
-
Since the supervision of stream elements is going to place restrictions on the actors, I think that providing a mixin “stream nature” might not be nicely manageable. Instead I propose a Source that ma…
rkuhn updated
9 years ago
-
Detailed code and stacktrace here: https://gist.github.com/knewter/16f001cbdb533f386c6b
Had a discussion with @halorgium on IRC, he requested that I /cc @benlangfeld since it's supervision-related.
…
-
It seem like the code in `OneBoundedInterpreter.execute` skips using the decider for all but the very first exception it encounters for single op flows.
See question here https://groups.google.com/d/…
-
I'm using the following example code (taken from https://github.com/celluloid/celluloid/wiki/Supervision%20Groups):
``` ruby
require "celluloid"
class Person
include Celluloid
def initialize(ag…
-
ktoso updated
9 years ago
-
In the scenario of an actor terminating repeatedly, the supervisor may handle the exit event while the previous exit event is still being handled.
There is no easy way to guard against this, but we s…
-
I've been doing something like this:
``` ruby
class MyApp < Celluloid::SupervisionGroup
supervise Foo, as: :foo
supervise Foo::Bar, as: :foo_bar
end
```
The `Foo` actor would then be the only ac…
-
Per discussion on #503 and #505, we are making a breaking change to `master` but will keep the old-style API in `0-16-stable` ... the breakage will be as follows:
There will be no `supervise`, `super…
-
I have a situation where I am customizing the behavior and details of a SupervisionGroup. Using pools works just fine, but if I want to supervise only one actor, it appears as though the registry isn'…