You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I know, right now the init-key is called just after spec validation (without validating all others specs). The proposal is have an option to validate first all the config, then initialize all.
This proposal is motivated because of this case use:
I proceed starting system, http server pases validtion and starts.
The next pre-init-spec fails, and leaves the system in failed state.
Now i'm unable to properly stop the jetty, and i can't restart because port is already used by the running jetty that i don't have access to. -> so I need to restart my repl process.
Validating all the specs before starting will help alot prevent this kind of situations.
The text was updated successfully, but these errors were encountered:
As far as I know, right now the init-key is called just after spec validation (without validating all others specs). The proposal is have an option to validate first all the config, then initialize all.
This proposal is motivated because of this case use:
Validating all the specs before starting will help alot prevent this kind of situations.
The text was updated successfully, but these errors were encountered: