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
Is your feature request related to a problem? Please describe.
Currently the application implements a hard cut-off date when the new protocol should be live. When running in non-interactive mode, this will cause our containers to crash-loop (obviously when there's no updated release before the deadline).
Describe the solution you'd like
Make it (an option) to warn about the deadline, but not crash. Although the purpose of the check is clear, we don't want our containers to crash.
Describe alternatives you've considered
Forking the repository and changing the deadline date manually or remove the code to exit the program
Is your feature request related to a problem? Please describe.
Currently the application implements a hard cut-off date when the new protocol should be live. When running in non-interactive mode, this will cause our containers to crash-loop (obviously when there's no updated release before the deadline).
Describe the solution you'd like
Make it (an option) to warn about the deadline, but not crash. Although the purpose of the check is clear, we don't want our containers to crash.
Describe alternatives you've considered
Forking the repository and changing the deadline date manually or remove the code to exit the program
Additional context
tezos-reward-distributor/src/launch_common.py
Line 79 in 9e20ab3
The text was updated successfully, but these errors were encountered: