Best IT Recipes

Fog and AWS Warning: Unreleased Stone Cannot Be Loaded

Each action in the rails console (rails server, rails console, db: migrate, etc.) raises a warning since the last package update:

[fog][WARNING] Unable to load the 'unf' gem. Your AWS strings may not be properly encoded.

I am sure that nothing has changed in the AWS lines that are in my application.rb file:

  # Amazon S3 credentials ENV["AWS_ACCESS_KEY_ID"] = "AWS_ACCESS_KEY_ID" ENV["AWS_SECRET_ACCESS_KEY"] = "AWS_SECRET_ACCESS_KEY" ENV["AWS_S3_BUCKET"] = "my-bucket"

I do not have this "non-local" gem in my gemfile. Should I add it?

+58
ruby ruby-on-rails amazon-web-services fog
Oct 29 '13 at 18:22
source share
3 answers

Yes, it happened just a few days ago. You can see from the migration request and commit that an optional dependency is optional.

https://github.com/fog/fog/pull/2320/commits

When I updated my current fog package, I received the same warnings and added

 gem 'unf'

really removes the warning without any problems.

+74
Oct 29 '13 at 18:38
source share

If you do not have S3 buckets / objects that would not have ASCII characters in the names, I think you can safely ignore this warning. We can do something to make it less noisy, but for now, you can ignore or add an inability to calm him, as @trh noted.

+13
Oct 30 '13 at 0:30
source share

I apparently had fog-1.18.0 installed when I saw this error. (Restarting the awas-roaming project that I installed some time ago) My naive attempt to fix it was to start by updating

  gem install fog

which updated something to fog-1.21.0. As he warned: "It may take some time ..." ... and it did not help.

Exactly WHERE to add "gem" unf "was not clear from the solution that voted here, it was lib / fog / aws.rb, but it was already there when I looked.

  gem install unf

appeared to add it somewhere, but the problem did not disappear.

I updated the tramp (1.4.3 to 1.5.1) and this did not fix it.

In the end, the fix was

  vagrant plugin install unf

as I found in the stream at https://github.com/mitchellh/vagrant/issues/2507

I'm not sure that any of my previous attempts at revival were also necessary, so I noted them here anyway.

+7
Mar 22 '14 at 2:08
source share


More articles:


All Articles