uninitialized constant S3Relay::PrivateUrl::Addressable about s3_relay HOT 7 CLOSED

@spovich
perhaps caused by your changes in 744906c?

from s3_relay.

@andmej we are using this fine in production on a Rails 5.1 project. From the error message, it appears that it is not finding addressable, but it is a runtime dependency: https://github.com/kjohnston/s3_relay/blob/master/s3_relay.gemspec#L21 So, maybe you need to re-bundle? Check your Gemfile.lock for addressable.

from s3_relay.

@spovich also seeing this issue. Had to add the require back in from f2cb06d to get it to work for me.

from s3_relay.

@andmej how did you end up tackling this? @ctmaloney I suppose it wouldn't hurt to add the require back to the top of that file, feel free to open a PR.

from s3_relay.

The same error here with a clean new 5.1 rails project. Fixed by creating
config/initializers/buggy_s3_relay_fix.rb

require 'addressable'

from s3_relay.

same issue
rails 5.2
s3_relay 0.7.0

from s3_relay.

@yunixon, I was able to upgrade an app to 5.2 recently and did not run into this issue. Please see @spovich's comment above about ensuring your Gemfile.lock is pulling in the addressable runtime dependency defined by s3_relay. If that doesn't work, try @artemf's workaround. I'll be discontinuing support for s3_relay as ActiveStorage now provides a more robust golden path solution, so when you get the chance to make the switch please do. I'm down to just one app relying on this gem at this point, but won't be moving it over immediately.

from s3_relay.