Sergiy Kukunin

The workaround is to add these lines to `spec_helper.exs`: ```elixir Process.unregister(ExUnit.CaptureServer) {:ok, _} = Application.ensure_all_started(:ex_unit) ```

It doesn't solve since both espec and ex_unit starts `ExUnit.CaptureServer`. So whoever starts it second, it crashes with `already running`. That's why I do ` Process.unregister(ExUnit.CaptureServer)` first

Downgrading compress to the lower version helped me go get github.com/klauspost/compress/[email protected]

I successfully manage to install `active_admin` with `vite_ruby` (ViteJS): To handle the `undefined method assets` while running `rake activeadmin:install`, I temporary installed `gem 'propshaft'`. Later the gem is not needed....

Rubocop limit was increased previously too https://github.com/ruby-grape/grape/commit/28d34ee19bdf70cb8471535b4c76312d440a63a6#diff-74423563ec7c74f4cb7f74689b49e7c1R47, and I believe to refactor it, a person should a better insight about grape than I have. So I increased limit by 3...

Thanks for the review. Will try to fix the issues later today or tomorrow

hi @dblock. do you mean that it'd be good to finalize and get this PR merged? If yes, then it's something I can do

How would you express the goal to capture response time metrics along with status code with `elixometer`? Have a unique metric for each status code? The information I would get...

Actually, the exometer_influxdb reporter already supports a feature to convert a chunk of metric as a tag: https://github.com/travelping/exometer_influxdb/issues/3 Someone might find this helpful, so I'm still posting the comment

I can start a little (I started using it yesterday) - auto-registration of metrics. I just put whatever metric I want to report - it provides a neat `@timed` annotation,...