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
I have been using Supervisor for development, and it irks me that if I make a syntax error or something else that will make Node crash immediately when launched, Supervisor will just continue to restart the process, several times a second.
Wouldn't it be a safe assumption that a process that dies within its first second of runtime should not be restarted?
The text was updated successfully, but these errors were encountered:
I agree, the instant infinite crash loop is a bit annoying. However, I always found it equally annoying when it bailed and I had to tab back into that terminal to restart supervisor just because I made a syntax error.
I've been thinking the best solution might be an exponential backoff, where the first crash within a given time period gets no delay, but subsequent crashes get longer and longer delays, up to 5s or something reasonable like that.
I have been using Supervisor for development, and it irks me that if I make a syntax error or something else that will make Node crash immediately when launched, Supervisor will just continue to restart the process, several times a second.
Wouldn't it be a safe assumption that a process that dies within its first second of runtime should not be restarted?
The text was updated successfully, but these errors were encountered: