klesh opened a new pull request, #5609: URL: https://github.com/apache/incubator-devlake/pull/5609
### Summary Due to #4864 had been introduced, there are a couple of side effects that must be taken care of: 1. What if a scope gets deleted while related pipelines are still running(users may remove the scope from the project while there is a pipeline running, so it is possible for the user to delete it on the Connection page): some unwanted data would be produced and they are hard to be identified and removed 2. What if a new pipeline gets created while deletion is in progress: this is unlikely to happen when the deletion is quick, but it might when the number of records is huge, especially after we support Cascade Connection Deletion. This PR makes pipeline-execution and scope-deletion mutually exclusive to prevent the above things from happening. **NOTE: We should reconsider most of our operation and consider wrap them inside Transaction due to Deletion Support** ### Screenshots Deleting scope while any pipeline is running would return error:  The Config-UI need to adopt the new error response format to show message correctly: @mintsweet the `Data` is renamed to `data`   Triggering pipeline while any deletion is taking place would be blocked until deletion finished  -- 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]
