has anyone else noticed broken spec coercion test with swagger app profile?

just "lein new luminus myapp +swagger && cd myapp && lein test"

coughs up this :

Request coercion failed: #reitit.coercion.CoercionError{:spec #Spec{:form (clojure.spec.alpha/keys :req-un [:spec$18482/x :spec$18482/y]), :type :map, :leaf? false}, :problems #:clojure.spec.alpha{:problems ({:path [:y], :pred clojure.core/int?, :val "invalid", :via [:spec$18482/y], :in [:y]}), :spec #Spec{:form (clojure.spec.alpha/keys :req-un [:spec$18482/x :spec$18482/y]), :type :map, :leaf? false}, :value {:y "invalid", :x 10}}}

maybe the middleware order is wrong?

And to be clear , it's not just a failed test, it's actually throwing an Exception and interrupting the test run - correction , the tests don't get interrupted, it's working as designed

ahh you know what I think I figured it out - it's as designed

it dumps the stacktrack to the console in the exception handler code, but it actually does then hand off the correct response code, and the total errors in the test report is 0

just could look prettier , imho the stacktrack (while useful) also makes it look like something's broken , not just a failed test

matter of preference though , easy enough to remove