-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update WebJobsScriptHostService to remove hardcoded sleep during shut down #9520
Conversation
Are we backporting this? I see you said no above.
|
@mathewc we're no longer backporting any changes. Do you think this change should be considered? |
I agree that we don't need to do a special v3 release for this, but if we end up needing to do one in the future for other reasons, it'd be good to have this change in there as well I think. |
That's fair, there's no harm in backporting any who |
/backport to v3.x |
Started backporting to v3.x: https://github.com/Azure/azure-functions-host/actions/runs/6125295823 |
@liliankasem backporting to v3.x failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Update WebJobsScriptHostService.cs
Applying: Update release_notes.md
Using index info to reconstruct a base tree...
M release_notes.md
Falling back to patching base and 3-way merge...
Auto-merging release_notes.md
CONFLICT (content): Merge conflict in release_notes.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 Update release_notes.md
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
Backport here: #9521 |
Issue describing the changes in this PR
resolves #8681
Pull request checklist
release_notes.md
Additional information
Antares does not rely on the flag
FUNCTIONS_ENABLE_DRAIN_ON_APP_STOPPING
– so we can safely assume that this code path is only used in LIMA. Speaking to the LIMA team we learnt that the time for sleep is inconsequential for the LIMA scenario and therefore should be safe to remove.