-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsuccessful deployments show up as successful when deploying from modeler #838
Comments
Would be extremely helpful to surface model parsing errors in the modeler. I see errors using the API but modeler just says deployment succeeds for the same file. |
Create Deployment endpoint does respond with an error - HTTP 500 - when I try to deploy a definition with a process-level Event Subprocess triggered by a Compensation Start Event (not supported according to the doc):
I'm not a JS expert, but as I understand, deployment logic is located in app/lib/createDeployer.js, and, as far as I see in fetch() docs, 500 won't lead to throwing an error. |
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
Closed via #1041. |
* use endpoint url provided by client * display user-friendly error messages * do not throw error for response other than JSON Closes #838
If I deploy a model directly from the modeler, it says "Deployment was done successfully" even if this was not the case. My engine complained with a BPMN parse error and did not deploy the diagram, but the modeler did not catch that problem.
v 1.16.0
The text was updated successfully, but these errors were encountered: