| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| netSocket.destroy(); | ||
| assert.strictEqual(netSocket.destroyed, true); | ||
|
|
||
| setImmediate(() => { |
There was a problem hiding this comment.
No common.mustCall here?
Sorry, something went wrong.
There was a problem hiding this comment.
We have separate tests for setImmediate().
Sorry, something went wrong.
There was a problem hiding this comment.
I don't really get what you mean, common.mustCall wouldn't be there to validate setImmediate behavior, but to ensure the assertion are actually run. Anyway, it doesn't really matter.
Sorry, something went wrong.
There was a problem hiding this comment.
We are testing that the callback of setImmediate() is called in other tests.
Sorry, something went wrong.
There was a problem hiding this comment.
It's not called if e.g. process.exit is called before it's picked up
Sorry, something went wrong.
There was a problem hiding this comment.
There is no process.exit() in the test.
Sorry, something went wrong.
There was a problem hiding this comment.
Adding common.mustCall would ensure we catch it if it was ever added
Sorry, something went wrong.
There was a problem hiding this comment.
I've added it only where it is needed given the current assumptions. If the logic changes there are other more places where it would be needed.
Sorry, something went wrong.
| let serverTlsSocket; | ||
| const tlsServer = tls.createServer({ cert, key }, (socket) => { | ||
| serverTlsSocket = socket; | ||
| socket.on('data', (chunk) => { |
There was a problem hiding this comment.
No common.mustCallAtLeast?
Sorry, something went wrong.
There was a problem hiding this comment.
No, only one byte is sent by the other peer.
Sorry, something went wrong.
Fixes: nodejs#49902 PR-URL: nodejs#53019 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
| Back | FazBrowse Home | New Git URL |
Fixes: #49902