Open JaeAeich opened 9 months ago
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 wes_client,
the WES API itself? Any idea where the issue might be arising from?
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 CORS
errors.
To debug I tried logging everything and checked if it was raising any errors that were not caught.
But today for some reason I encountered another issue, /runs endpoint is working but /cancel/:id
is throwing a 500
error, ie could not reach remote wes service
.
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! :sweat_smile:.
Describe the bug The
/runs/:id/cancel
is not working as expected. It throws aCORS
error.Response:
Traceback:
To Reproduce
/runs
endpoint.