I’m sometimes getting these "error-stylobate triggered"
errors in the logs for the cljdoc production server. So far i hasn’t been a big issue but since it logs the entire context I think it’s causing the server to become unresponsive somehow. Maybe I’m completely wrong here but how people deal with this usually? I found this but would rather not do that: https://github.com/tonsky/grumpy/commit/c6bbcc9590394243e37c2a72a4e569a7c506be7d
Hi @martinklepsch, error-stylobate
is intended to be a catchall. Apps are recommended to implement their own error handling interceptors.
@ddeaguiar Thanks, so you mean I should just have a catch all interceptor myself & this way avoid the stylobate logging thing?
Yep
Ok cool, thanks!