carloea2 opened a new issue, #8089: URL: https://github.com/apache/texera/issues/8089
## What happened? Root cause: `NetworkOutputBuffer` accepts a batch size of zero or less. Its size check then becomes true after every tuple, so invalid API input silently changes buffering into one message per tuple. Before: A nonpositive batch size is accepted and every tuple is sent immediately. Expected: Construction rejects a nonpositive batch size. ## How to reproduce? 1. Check out main at commit `d9c0e19aeed027c4a61d746d875a8b46dd1db568`. 2. Run the `NetworkOutputBufferSpec` suite. 3. Observe that the characterization test accepts zero and negative sizes while the rejection test is pending. The runtime suite completed with 17 successful tests and 1 pending test. ## Version and branch Main, version 1.3.0 incubating snapshot. ## Commit hash `d9c0e19aeed027c4a61d746d875a8b46dd1db568` ## Browsers Not applicable. This is an Amber network buffering issue. ## Relevant log output ```text Total number of tests run: 17 Tests: succeeded 17, failed 0, canceled 0, ignored 0, pending 1 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
