-
Notifications
You must be signed in to change notification settings - Fork 5
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
cancel endpoint not working #86
Comments
Hey @uniqueg, I have checked this out and can't seem to find where the issue might be coming from; I have checked commits as far as last year but still have the same result. Could there be an issue with the |
I don't know either. First of all: Did you verify if it works if you try to cancel runs via Swagger (at least that should not give a CORS error). What other steps did you do to debug? |
Yeah, no But today for some reason I encountered another issue, /runs endpoint is working but |
Is this on a local deployment via Docker Compose? If not, can you try it locally and check the error trace? I really think that cancellation in proWES was never properly implemented. It might be that it's just a line or two that need changes, but it could also be something bigger. Do you actually need this function? I think as long as you don't get a 400 reply, your client should be sending the right request, so the problem is not really on your side. To further check if your client behaves as expected, you could check whether cURL and the Web Component give different results (setting aside the CORS issue). |
Yeah, this is not needed for the Web Components, I was checking the issue independent of that, hope thats ok! 😅. |
Describe the bug
The
/runs/:id/cancel
is not working as expected. It throws aCORS
error.Response:
Traceback:
To Reproduce
/runs
endpoint.The text was updated successfully, but these errors were encountered: