carloea2 opened a new issue, #8097: URL: https://github.com/apache/texera/issues/8097
## What happened? Root cause: AcquireLockRequest reads the collaboration lock holder map with direct indexing even when the workflow has no holder entry or stores the null no-holder marker. Before: requesting an unheld lock raises NoSuchElementException and the client receives no lock event. Expected: the requester becomes the holder and receives LockGrantedEvent. ## How to reproduce? 1. Start Texera locally. 2. Open an anonymous connection to the collaboration WebSocket. 3. Register a workflow and send AcquireLockRequest while no holder exists. 4. Observe that the client times out and the server logs NoSuchElementException. The same failure occurs after a holder disconnects and leaves the null no-holder marker. The focused regression suite reproduced both states with 27 tests passing and 2 failing. ## Version or branch 1.3.0-incubating-SNAPSHOT on main ## Commit hash 2173ec57fc ## Browsers Not browser specific. Reproduced through the live localhost WebSocket endpoint. ## Relevant log output java.util.NoSuchElementException: key not found -- 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]
