If a user sets a custom duration timeout, since the value gets pulled from the environment and isn't detyped, it comes in as a string and then breaks because of a > comparison between a number and a string.
In the long run, probably good to add proper detyping, but for now, this makes things not break.
If a user sets a custom duration timeout, since the value gets pulled from the environment and isn't detyped, it comes in as a string and then breaks because of a
>
comparison between a number and a string.In the long run, probably good to add proper detyping, but for now, this makes things not break.