The GitHub Actions job "Required Checks" on texera.git/fix/scan-window-bound has succeeded. Run started by GitHub user kz930 (triggered by kz930).
Head commit for run: 76c98b3939db6a517a547d75bc38bf563aa95259 / kary zheng <[email protected]> feat(source): bound a file scan's window at zero Every file-scan source takes a Limit and an Offset from ScanSourceOpDesc, and neither said it cannot be negative. Neither means anything below zero, and a negative one is not read the same way twice: the executors take the window with `drop` and `take`, where a negative drop keeps every row and a negative take keeps none, while the scripts the export writes take it with `iloc`, which counts from the end. `offset = -1` is every row on one side and the last row on the other. Declaring the bound on the two fields states what the operators already assume, and the property editor then refuses the value. It reaches CSV, CSVOld, JSONL, Arrow and the file scans at once, all of which inherit the fields. No executor changes: a plan submitted through the API can still carry a negative, and nothing about how one is processed is touched here. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/34577552803 With regards, GitHub Actions via GitBox
