carloea2 opened a new pull request, #8298:
URL: https://github.com/apache/texera/pull/8298

   ### What changes were proposed in this PR?
   
   Report per-row MainLoop failures through the worker exception path, enter 
exception pause, and stop consuming the affected batch.
   
   Before: the worker logged the failure, continued later rows, and could 
finish with missing output.
   
   After: the coordinator receives the error and the batch stops at the failed 
row.
   
   ### Any related issues, documentation, discussions?
   
   Closes #8297
   
   ### How was this PR tested?
   
   Added a regression covering the failure report, exception pause, and stopped 
batch consumption.
   
   ```powershell
   $env:PYTHONDONTWRITEBYTECODE='1'; 
C:\Users\carlo\texera\texera\.venv312\Scripts\python.exe -c "import sys,pytest; 
sys.path[:0]=[r'C:\Users\carlo\texera\texera-worktrees\investigate-bug78\amber\src\main\python',r'C:\Users\carlo\texera\texera\amber\src\main\python'];
 raise 
SystemExit(pytest.main([r'amber/src/test/python/core/runnables/test_main_loop.py::TestMainLoop::test_failing_element_reports_exception_and_stops_batch','-p','no:cacheprovider','-q']))"
   C:\Users\carlo\texera\texera\.venv312\Scripts\ruff.exe check 
amber/src/main/python/core/runnables/main_loop.py 
amber/src/test/python/core/runnables/test_main_loop.py
   C:\Users\carlo\texera\texera\.venv312\Scripts\ruff.exe format --check 
amber/src/main/python/core/runnables/main_loop.py 
amber/src/test/python/core/runnables/test_main_loop.py
   ```
   
   The focused regression passed. The full MainLoop test file was also run: 36 
tests passed and 8 pre-existing integration cases failed during executor 
initialization because the shared generated protocol files do not yet contain 
`loop_start_port_uris`.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: OpenAI Codex
   


-- 
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]

Reply via email to