Raido
Raido
@benkoshy What do you mean it's running perfectly. The example code currently don't raise any errors. When I dup record and change image in duped record, then original record image...
With that solution it's unclear for me, if I have to call `AppSignal.start` manually. And If I want to extend options `+=` then I have to `Appsignal::Config::DEFAULT_CONFIG[:request_headers] + %[HTTP_X_CUSTOMER_HEADER]` not...
Do I have to call any other methods manually like integerations (Sidekiq, Redis) or all other things are automatically done? For example https://docs.appsignal.com/ruby/integrations/rack.html is called start_logger. It would be nice...
Any updates with merging this?
@stuyam can you approve the CI workflow for this PR as this adds better support for Debian 11?
The documentation says that the `transform_path` **transformation will be applied to all API path values in the generated `api-docs.json` file**, so this does NOT change the location of generated docs....
What is the status of the fix and is there any estimates when this PR may merged and released?
@ixti or @holstvoogd any progress with this?
This seems to work with Sidekiq 6 Pro. With the v1.0.0.alpha version pause/unpause works and concurrency is also handled correctly. The capsules where introduced in Sidekiq 7.
Is there any progress with this?