malli.error/humanize can reduce the error size, but I'm not sure if you've already tried that or if it will suffice for your problem.

how are you performing the validation? could you do something like (assert (m/validate X Schema) (-> X (m/explain Schema) (me/humanize)))?

a more general purpose solution might be to defer your error logging to an async logging library like https://github.com/BrunoBonacci/mulog, which provides a ring buffer mechanism that you can hook into with custom transformation functions to output errors and logs that narrow down to the specific thing you're trying to investigate.

I forgot to tell that humanization doesnt work for me.. for unknown reason, this is my coercion in reitit-hander. It would probably help a lot.

(r.coercion.malli/create (-> r.coercion.malli/default-options                                                                          (assoc :strip-extra-keys true)                                                                   (update :error-keys #(conj % :humanized))))

@UFTRLDZEW i use timbre currently, but i would like to solve that problem on malli / emacs level first.

several minutes 🙀

Oh, the error is not related to reitit coercion. It is invalid return output value…

@U055NJ5CC Yeah, vscode got it in second.

do you have the pretty printing turned on?

the colored outputs can be slow, dunno if there is a bug in rendering, fipp is supposed to be fast.

but, not an emacs user (anymore), so not sure what happends there, if calva is fast with the same case.

Did you switch to vscode? Yeah, i do, i will try to disable it, thanks. Is there some easy way for instrumented fns to produce only humanized errors?

• disabling pretty/reporter for instrumentation helped a lot.. closing other windows in emacs as well 😄.