Skip to content

Set the Runner :timeout option to the maximum between itself and the :boot_timeout - #73

Open
probably-not wants to merge 1 commit into
phoenixframework:mainfrom
probably-not:main
Open

Set the Runner :timeout option to the maximum between itself and the :boot_timeout#73
probably-not wants to merge 1 commit into
phoenixframework:mainfrom
probably-not:main

Conversation

@probably-not

Copy link
Copy Markdown
Contributor

Currently, the :timeout and :boot_timeout are separate options - however, when running something that has a long :boot_timeout set, you must know to set the :timeout option to the same time (or longer), otherwise, the FLAME.call function calls will fail with a timeout even if the boot has not completed.

This PR sets the :timeout option to be the maximum between the :timeout and the :boot_timeout, to ensure that a timeout cannot happen before a boot_timeout happens.

@lessless

Copy link
Copy Markdown

Currently, the :timeout and :boot_timeout are separate options - however, when running something that has a long :boot_timeout set, you must know to set the :timeout option to the same time (or longer), otherwise, the FLAME.call function calls will fail with a timeout even if the boot has not completed.

This PR sets the :timeout option to be the maximum between the :timeout and the :boot_timeout, to ensure that a timeout cannot happen before a boot_timeout happens.

That sounds like it's worth a mention in documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants