Closed pcrespov closed 5 days ago
@pcrespov yes, 422 is the status code we agreed for letting the users know that the pipeline is up-to-date, but they might still want to force a re-run.
Error code-wise might not be correct, but as long as all parts are in sync, we are fine.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 85.1%. Comparing base (
cafbf96
) to head (2f2ae3f
). Report is 298 commits behind head on master.
What do these changes do?
Mismatch between the error code specified in the OAS and the actual error code when starting a computation.
Related issue/s
How to test
Dev-ops checklist
None