-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reevaluating a cell containing Kino.start_child! sometimes errors with "Already started" #397
Comments
Can you provide the stacktrace as well? Even if not consistent, can you provide the code? Or can you tell us if it happens if you have a very simple GenServer as children? The reason I ask is because when we re-execute a cell, we terminate all previous children. So I can think of two options here:
|
Sorry for the delay! I will provide a stacktrace the next time it happens! The structure of the code looks like this: Elixir cell 1: define a GenServer The GenServer does not start any other GenServers, but it does call other ones, also by name, if that matters! |
Do you call Also, for the reference, what Kino and Livebook versions do you use? |
@jyc ping :) |
Directly in the code cell!
v0.12.1 I've been using Elixir for a component of my current project that I haven't touched in a month, because I've been working on other components. So unfortunately I don't have any new stacktraces to give you. But I expect to get back to the Elixir part soon! |
Hello!
Thanks for making Kino.
I'm using some GenServers inside of a Livebook notebook. I have an Elixir cell which contains a call to
Kino.start_child!/1
.Weirdly, sometimes when I reevaluate the cell, it works fine and I get
#PID<0.4995.0>
. Other times I get an error about a process already being started.Do you know what's going on? Unfortunately the error is nondeterministic so I'm unable to create a minimal reproducible example, but I'm happy to help investigate.
The text was updated successfully, but these errors were encountered: