Mojolicious 9.0 compatibility
Mojolicious 9.0 has just been released and there are quite a few breaking changes. Some also affect openQA, such as the use of reserved stash values as route placeholders, and need to be fixed.
- Category set to Concrete Bugs
- Target version set to Ready
I think we should consider this part of the backlog and effectively a bug fix, because we'll be in trouble if we want to use the latest Mojolicious.
Thank you, kraih, for being on top of it. Although I would prefer the API wasn't broken all the time, but well, it is what it is.
No it's not just "for fun". :) The things i've found in openQA so far are actual bugs, like
/:status being used as a route placeholder. And
status is special because it allows the response code to be changed (
$c->render(text => '...', status => 302)). So we might end up allowing the request URL to pick a specific response code. You get the idea. Mojolicious 9.0 turned a lot of these easy to make mistakes into exceptions.
And yes, once 9.0 reaches factory our tests would fail.
#10 Updated by SLindoMansilla 5 months ago
Executing /usr/share/openqa/script/openqa-gru fails
# output of /usr/share/openqa/script/openqa-gru [2021-02-17 13:07:06.55734]  [warn] Deprecated use of config key '[audit]: blacklist'. Use '[audit]: blocklist' instead Route pattern "/children/:status" contains a reserved stash value at /usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 361. # exit code 30