carloea2 opened a new issue, #8197: URL: https://github.com/apache/texera/issues/8197
## What happened? InputManager updates its channel-to-port mapping when an existing channel is registered on a new input port, but it never removes that channel from the old port's reverse channel set. Port-aligned control messages use those reverse sets, so an old port can continue waiting for a channel that has been reassigned. Before: the forward mapping points to port 1 while both port 0 and port 1 contain the channel. After: the channel belongs only to port 1, and the forward and reverse mappings agree. ## How to reproduce? 1. Add input ports 0 and 1 to an InputManager. 2. Register one data channel on port 0. 3. Register the same channel on port 1. 4. Observe that get_port_id reports port 1. 5. Observe that get_channels on both ports still contains the channel. ## Version/Branch 1.3.0-incubating-SNAPSHOT (main) ## Commit Hash 70c21145887920528d7d5540e3fb790b43e8b759 ## Relevant log output forward_port=1 port_a_channels=1 port_b_channels=1 present_in_both=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]
