Skip to content
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

Pass callback directly to connect, reconnect #12

Closed
wants to merge 1 commit into from

Conversation

doesdev
Copy link

@doesdev doesdev commented Jan 22, 2020

This is to ensure that initial socket connection errors are caught.
Alternatively, we could push the callback into the queue before calling
connect. However, that has potential side-effects. I went for the
solution with the least chance of unintended consequences.

This is to ensure that initial socket connection errors are caught.
Alternatively, we could push the callback into the queue before calling
`connect`. However, that has potential side-effects. I went for the
solution with the least chance of unintended consequences.
@doesdev
Copy link
Author

doesdev commented Jan 23, 2020

Nevermind, there are some issues with this. That is, it does not resolve the issue save for the very first call. Will work on a better solution.

@doesdev doesdev closed this Jan 23, 2020
ronag pushed a commit that referenced this pull request Jan 13, 2022
* fix: 'same origin' & setting response

* fix: remove httpRedirectFetch step #12
KhafraDev referenced this pull request in KhafraDev/undici Jun 23, 2022
* fix: 'same origin' & setting response

* fix: remove httpRedirectFetch step #12
crysmags pushed a commit to crysmags/undici that referenced this pull request Feb 27, 2024
* fix: 'same origin' & setting response

* fix: remove httpRedirectFetch step nodejs#12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant