Conversation
🦋 Changeset detectedLatest commit: 02b9fc3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Collaborator
Size Report 1Affected Products
Test Logs |
hsubox76
reviewed
Dec 3, 2024
Collaborator
Size Analysis Report 1Affected Products
Test Logs |
hsubox76
reviewed
Dec 4, 2024
hsubox76
approved these changes
Dec 4, 2024
Contributor
hsubox76
left a comment
There was a problem hiding this comment.
Approved with one minor nit.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We set a timeout to abort a request after 180s by default, but we don't cancel this timeout after the request completes. We should cancel this timeout after the request completes to prevent Node scripts from hanging.
I inlined everything in
buildFetchOptionsand removed that function. Let me know if I should revert this and initialize theAbortControllerin there- but I think the timeout-related code still has to be inlined so that we can get thetimeoutId.I tested this in a Node script using the default timeout and a custom timeout, and they both work as expected. If the timeout is triggered before the request completes, an
AbortErroris thrown. If the request completes before the timeout is triggered, the timeout is cancelled, and the Node script is able to exit.Fixes b/380936830 (internal)