Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warning: URI.escape is obsolete #559

Closed
dvenrao opened this issue Sep 9, 2020 · 1 comment
Closed

warning: URI.escape is obsolete #559

dvenrao opened this issue Sep 9, 2020 · 1 comment

Comments

@dvenrao
Copy link

dvenrao commented Sep 9, 2020

We are seeing below warnings with ruby 2.7.0 and docker-api-1.34.2:

/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/container.rb:346: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/image.rb:129: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/container.rb:346: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/image.rb:129: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/container.rb:346: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/image.rb:129: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/container.rb:346: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/container.rb:346: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/container.rb:346: warning: URI.escape is obsolete
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/docker-api-1.34.2/lib/docker/image.rb:129: warning: URI.escape is obsolete

@tlunter
Copy link
Contributor

tlunter commented Sep 11, 2020

@dvenrao we've just released docker-api v2 which has minor code removal, and fixes this issue. I'm not sure if @tas50 has forced users of chef over to their fork, but this latest release should resolve those issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants