Paul Schoenfelder

@bryanhuntesl Sorry for the delay, haven't had a chance to get back to this in a while. I'm good with renaming the strategy, and documenting the caveats. I'll have to...

@dax0 yes, though in the current example it shouldn't be restarted since the restart type is `:temporary` (meaning that if it fails, it is not restarted)

With simple_one_for_one, if the process exits with :normal, :shutdown, or `{:shutdown, term}`, it won't be restarted. How are you simulating the crash?

@bschaeffer Yes, if you have a need for supervising the processes being dynamically registered, you have to link/monitor those children and handle restarting them yourself currently - I would like...

@kwrooijen I was referring to the first part of my comment, which is supervising children directly by linking/monitoring them and reacting to down/exit signals appropriately - this is what Supervisor...

Just an update here: To properly handle supervision, support needs to exist _within Swarm itself_, at least for things which use `register_name/5` to handle auto-distribution and the like. This is...

@kelostrada How are you handling the case where the cluster topology changes? Swarm assigns processes started via `register_name/5` based on how the name is sharded across a hash ring containing...

Specifically, my suggestion was that the `--alias` flag would be for `asdf install : [--alias=]`. For other forms of `asdf install `, `--alias` would produce a warning/error (my opinion is...

RE: 4, my intuition around `asdf uninstall [path:|]` is that it simply unlinks the symlink created by "install" (rather than deletion, as you obviously don't want that), and in the...

@Stratus3D I'm willing to work on `asdf` and in particular be responsible for this feature. I'm certainly familiar with the burden of maintaining open source projects. If that's the major...