fix(node-http-handler): set maxSockets above 0 in test

[mhart]

Issue #, if available:

#1539

Description of changes:

Just browsing, but it looks at first glance like the issue with the test is that maxSockets will sometimes be set to 0 – due to Math.random() and Math.round(). My guess is that a setting of maxSockets = 0 gets turned into Infinity – so the test will fail in these cases. This change ensures maxSockets will always be at least 1 in this test.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[trivikr]

Thank you @mhart for your first PR. I've added nits to use Math.ceil instead.

Tested in Chrome Developer Tools:

> Math.ceil(0.00001)
1

[mhart]

Thank you @mhart for your first PR. I've added nits to use Math.ceil instead.

Tested in Chrome Developer Tools:

> Math.ceil(0.00001)
1

Yeah, but Math.ceil(0) === 0 😉

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.