beepboop
DynamicSupervisor - why does it ignore exit signals from non-child processes?
DynamicSupervisor traps exit signals and handles ones coming from its children:
However, it also implicitly ignores exit signals from non-child processes: elixir/lib/elixir/lib/dynamic_supervisor.ex at 427d21e410d1846c232d0a0b0e87cce629884dfa · elixir-lang/elixir · GitHub
Does anyone know - is it an intentional design decision?
I’m trying to link it to a process that’s not its direct parent/child, so it would exit when the other process exits, but of course at the moment it doesn’t work. I don’t care so much about my use-case per-se (I can figure out a solution), but I’m in general wondering if there’s a good reason for how DynamicSupervisor is implemented - i.e. maybe I’m doing something that goes against first principles?
Most Liked
hauleth
Make that proces being supervised by that supervisor instead, and then make it :significant (though I do not know if DynamicSupervisor supports that, but if that process is known to be there, then why it is part of DynamicSupervisor?).
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









