carloea2 opened a new issue, #8082: URL: https://github.com/apache/texera/issues/8082
## What happened? Root cause: `OperatorExecution.initWorkerExecution` calls `ConcurrentHashMap.contains`, which checks values instead of keys. A repeated worker ID therefore replaces the existing `WorkerExecution` even though the method contract says it must reject duplicates. Before: A repeated worker ID replaces the original execution. Expected: A repeated worker ID raises `AssertionError` and leaves the original execution registered. ## How to reproduce? 1. Check out main at commit `b59c7406d0a7d549a50c1f86888e85563f2d3446`. 2. Run `sbt "WorkflowExecutionService / Test / testOnly org.apache.texera.amber.engine.architecture.coordinator.execution.OperatorExecutionSpec"`. 3. Observe that the characterization test accepts replacement of the first execution and the intended duplicate rejection test is pending. The runtime test completed with 14 successful tests and 1 pending test. ## Version and branch Main, version 1.3.0 incubating snapshot. ## Commit hash `b59c7406d0a7d549a50c1f86888e85563f2d3446` ## Browsers Not applicable. This is an Amber coordinator issue. ## Relevant log output ```text Total number of tests run: 14 Tests: succeeded 14, failed 0, canceled 0, ignored 0, pending 1 ``` -- 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]
