| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Is it possible to add a test for this?
Sorry, something went wrong.
There was a problem hiding this comment.
There are already tests for it that have been flaky, this should fix those flaky tests. One of the existing ones could be modified to check that a secureConnect handler has been registered.
Sorry, something went wrong.
There was a problem hiding this comment.
@jasnell Can you point me to one? I volunteer to try and make it fail/pass consistently :)
Sorry, something went wrong.
There was a problem hiding this comment.
http2-create-client-secure-session is one, which should be fixed by this PR.
I've updated it to include the check for secureConnect
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM 👍
Sorry, something went wrong.
There was a problem hiding this comment.
Can you remove this and the associated function? They should not be necessary.
Sorry, something went wrong.
There was a problem hiding this comment.
Same as above.
Can you remove this and the associated function? They should not be necessary.
Sorry, something went wrong.
There was a problem hiding this comment.
Could this be a bit more descriptively named? (Similar to setupFn elsewhere in this code.)
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM 👍 This event confused me many times. Thanks for clearing it up.
Sorry, something went wrong.
General improvements to test and verify that a secureConnect handler is present
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Includes multiple cleanups in core.js along with:
/cc @nodejs/http2
Fixes: #15303
Checklist
Affected core subsystem(s)
http2