carloea2 commented on PR #8637: URL: https://github.com/apache/texera/pull/8637#issuecomment-6179513354
Thanks for the latest fixes. Could you check that suggestions and pending Apply operations are invalidated when the user switches workflows? At `e7c0d7b`, the root service tracks the operator ID but not the workflow/session identity, and the workspace's `Uninitialized` reset does not clear the suggestion or supersede an in-flight analysis. In an isolated service reproduction using the PR source with mocked dependencies, I started an analysis in workflow A, emitted that reset, switched the graph to workflow B with the same operator ID, then completed the response. Apply wrote the suggestion to B and requested its execution. This still needs browser verification; I have not confirmed the full navigation sequence end to end. Could you try two imports of the same workflow JSON and, if confirmed, bind analysis/Apply to the workflow session, invalidate them on a switch, and recheck the session after the asynchronous unlock wait? A regression test should verify that a response or Apply from A cannot modify or rerun B. -- 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]
