| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Clarify how it must behave for both synchronous and asynchronous completion.
|
@sam-github sadly an error occured when I tried to trigger a build :( |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
|
re-ci: https://ci.nodejs.org/job/node-test-pull-request/21112/ It's just a header file comment, but a good build is hard to find. :-( |
Sorry, something went wrong.
|
re-ci: https://ci.nodejs.org/job/node-test-pull-request/21115/ windows vs2017 failed across the board, looks like remotes couldn't get connected to, but perhaps I misread the log files |
Sorry, something went wrong.
|
Windows rebuild: https://ci.nodejs.org/job/node-test-commit-windows-fanned/25099/ |
Sorry, something went wrong.
|
This should not require a full CI run as it's a doc only change. Therefore this should be good to land without making sure all platforms are green. |
Sorry, something went wrong.
Clarify how it must behave for both synchronous and asynchronous completion. PR-URL: #26339 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Clarify how it must behave for both synchronous and asynchronous completion. PR-URL: nodejs#26339 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
| Back | FazBrowse Home | New Git URL |
Clarify how it must behave for both synchronous and asynchronous
completion.
@addaleax @nodejs/streams This documents my understanding of the StreamResource::DoWrite() API expectations. TLS wasn't obeying these expecations, leading to wide-spread test suite failures during TLS1.3 development.
Checklist