Viktor Sych
Viktor Sych
@delner hanami is just a rack based framework. So the issue is related to Rack::CommonLogger which is something which exists many years. Rack::CommonLogger is a part of rack library so...
@marcotc so as I understand the solution for rack middleware is: Insert datadog rack middleware on top of all middlewares, so trace/span is started for sure at the very beginning...
> > so technically datadog "rack" instrumentation is not complete without handling that CommonLogger properly. > > @skcc321 Right, so why couldn't we push the `datadog` middleware to the the...
@delner @ivoanjo any updates on this one?
@HungLe14 please check this solution https://github.com/williamboman/nvim-lsp-installer/issues/187#issuecomment-1283060818
Hi, there I faced the same issue due to `inherited_gem` in `.rubocop.yml`. according to the documentation https://docs.rubocop.org/rubocop/configuration.html#inheriting-configuration-from-a-dependency-gem it should be executed via `bundle install`. As we don't have `useBundler` option...
I faced with a similar problem - I expected changing log_level to "info" should disable SQL logs (similar to Rails logger) but it just does not work. When I change...
> Non-blocking Fibers @claudiug is it going to happen at all?
any updates on that one?
Guys you can use dry validation stand-alone. It has everything what you need for this case