Socket "readExactly" Helper

[SeanCheatham]

Purpose

• Socket.read may not produce all of the requested bytes
• The consumer assumes all bytes are available, so parsing is likely to fail
• This situation is only likely to happen when crossing physical network boundaries (i.e. local to GCP), but not in local connections

  Approach

• Add a helper which polls the socket (similar to the readN implementation but returning an Option instead)

  Testing

• preparePR
• This isn't something that is easily reproducible locally

  Tickets

• BN-1543

[github-actions[bot]]

Test Results (pull_request)

464 tests   464 :white_check_mark:  6m 24s :stopwatch:  87 suites    0 :zzz:  87 files      0 :x:

Results for commit dfd6a549.