Use exit/1 instead of Process.exit/2 on batch timeout #1348
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi 👋
#1298 replaced
Task.await
with a combination ofTask.shutdown
+Process.exit/2
in the case of timeout. This was theoretically an equivalent, as withTask.await
, if the timeout is exceeded the caller process exits. However,Task.await
usesKernel.exit/1
under the hood which AFAIK isn't equivalent toProcess.exit(self(), reason)
.Here's a single file demo of errors:
Script
This is 1.7.6 error with cowboy (before #1298)
On current main cowboy just hangs, but Bandit yields this error which demonstrates that execution continues after
Process.exit(self(), :timeout)
is called:Finally, with this PR the error as seen through Cowboy will be this:
Bandit does not handle process exit very well, but that's not new and a conversation for another ticket I think.