-
Notifications
You must be signed in to change notification settings - Fork 557
fix: timeoutSignal is lost after being overriden with controller.signal #2665
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
base: main
Are you sure you want to change the base?
fix: timeoutSignal is lost after being overriden with controller.signal #2665
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sachiniyer The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
That would be very helpful! |
Hi @cjihrig ! I've added a previously failing test. If you add back the line that I deleted, you will see that the test hangs/times out. I also made the timeout value a private instance property to make it more easily testable - hopefully that's alright. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM, thanks.
Made both adjustments @cjihrig Lmk if anything else looks off. |
I believe that the watch timeout abort signal was getting overwritten, and I think 0ae5ddf just forgot to delete line 44.
I wrote a one-off test to make sure this was really happening, but please let me know if I should be adding a unit test for this functionality as part of this PR.