aglinxinyuan opened a new issue, #6543: URL: https://github.com/apache/texera/issues/6543
### Task Summary The pyamber worker's MainLoop/DataProcessor handshake must complete a worker whose input port receives **zero tuples** across a `StartChannel` → `EndChannel` bracket — e.g. the untaken branch of an `If` operator read through an `InputPortMaterializationReaderRunnable`, or a filter that drops everything on a materialized edge. Such a worker never enters `RUNNING`, so it completes straight from `READY`. This path is currently unguarded by unit tests; on an earlier loop branch it regressed into a MainLoop/DataProcessor deadlock, and the loop-operator work (#5700) is what makes it correct on `main`. Add regression tests so it can't silently regress. | Test (`amber/src/test/python/core/runnables/test_main_loop.py`) | Guards against | | --- | --- | | zero-tuple `StartChannel`→`EndChannel` completes the worker | `_process_ecm` dispatching the marker with an intervening context switch (deadlock); a missing `READY → COMPLETED` transition | | empty `on_finish` after tuples completes the worker | losing the single-hand-off completion signal | The tests run the MainLoop on a daemon thread and deadline-poll `WorkerState.COMPLETED`, so a regression deadlock fails cleanly instead of hanging pytest. ### Task Type - [x] Testing / QA -- 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]
