Grzesiek Kolodziejczyk
Grzesiek Kolodziejczyk
For those looking for a workaround, you can set the secret key in your `devise.rb` initializer: ```ruby config.secret_key = Rails.application.secret_key_base ``` and you won't see the deprecation warning anymore.
I'm currently evaluating running actions on ubicloud and ran into an issue with the actions cache. Our bundler cache is ~650MB, and the download from the default cache location runs...
Is this gem necessary anymore? I think rails-i18n should cover this.
@piotrekbator could you check out the modernize branch? It should have tests passing on a modern ruby version, and hopefully work OK in a Rails app.
ruby-bin-version seems most logical
This makes `yarn install` run twice on each deploy though.
@ankurgupta if you still have this problem, it's related to `safe_yaml` and will be fixed by #84
There's a similar issue with clockwork - everything scheduled from the clockwork process inherits one huge trace. Ideally there should be an api to do something like ```ruby Sentry.without_trace_propagation do...