carloea2 opened a new issue, #8265: URL: https://github.com/apache/texera/issues/8265
### What happened? `InputPortMaterializationReaderRunnable.stop` prevents tuple replay, but the state replay loop does not check the stop flag. A reader stopped before or during replay can still deserialize and emit persisted state rows, changing downstream state after workflow cancellation. Before: stopping a materialized reader still allows state frames to be emitted. Expected: stopping the reader skips both state and tuple replay while still closing the channel. ### How to reproduce? 1. Create a materialized input reader whose state document contains a row. 2. Call `stop` before `run`. 3. Run the reader and observe that one `StateFrame` is still placed on the input queue. ### Version or branch 1.3.0-incubating-SNAPSHOT on main ### Commit hash 50321e403c82df299a13deb50a7f9849dd93bdba ### Relevant log output stopped=True state_frames_emitted=1 finished=True -- 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]
