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

Possible issue with xpath on 2.0.1 #880

Closed
subelsky opened this issue Nov 21, 2012 · 6 comments
Closed

Possible issue with xpath on 2.0.1 #880

subelsky opened this issue Nov 21, 2012 · 6 comments

Comments

@subelsky
Copy link

I just upgraded to 2.0.1 and got this error when I tried to run tests:

cannot load such file -- xpath
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `block in require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in `load_dependency'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/capybara-2.0.1/lib/capybara.rb:3:in `<top (required)>'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `block in require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in `load_dependency'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/capybara-2.0.1/lib/capybara/dsl.rb:1:in `<top (required)>'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `block in require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in `load_dependency'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
/Users/subelsky/code/adweb/.bundle/gems/ruby/1.9.1/gems/domino-0.2.1/lib/domino.rb:1:in `<top (required)>'
/Users/subelsky/.rvm/gems/ruby-1.9.3-p194/gems/bundler-1.2.1/lib/bundler/runtime.rb:68:in `require'
/Users/subelsky/.rvm/gems/ruby-1.9.3-p194/gems/bundler-1.2.1/lib/bundler/runtime.rb:68:in `block (2 levels) in require'
/Users/subelsky/.rvm/gems/ruby-1.9.3-p194/gems/bundler-1.2.1/lib/bundler/runtime.rb:66:in `each'
/Users/subelsky/.rvm/gems/ruby-1.9.3-p194/gems/bundler-1.2.1/lib/bundler/runtime.rb:66:in `block in require'
/Users/subelsky/.rvm/gems/ruby-1.9.3-p194/gems/bundler-1.2.1/lib/bundler/runtime.rb:55:in `each'
/Users/subelsky/.rvm/gems/ruby-1.9.3-p194/gems/bundler-1.2.1/lib/bundler/runtime.rb:55:in `require'
/Users/subelsky/.rvm/gems/ruby-1.9.3-p194/gems/bundler-1.2.1/lib/bundler.rb:128:in `require'
/Users/subelsky/code/adweb/config/application.rb:13:in `<top (required)>'
/Users/subelsky/code/adweb/Rakefile:8:in `require'
/Users/subelsky/code/adweb/Rakefile:8:in `<top (required)>'

I was able to fix it by explicitly adding xpath to my project's Gemfile but this doesn't seem like the expected behavior

@jnicklas
Copy link
Collaborator

Very odd, I just tried to replicate this, but was not able to. I saw someone on the mailing list who had a similar problem, but I dismissed it as an unrelated. Can you create a repo with just a Gemfile which replicates this issue?

@subelsky
Copy link
Author

I wasn't able to replicate it in a fresh repository. I did notice during this process that I had a dependency of @ngauthier's domino gem in my development group, which depends on Capybara. I moved it into the test group, re-bundled, and everything was fixed.

I'm closing this issue; if anyone else comes across problem this I recommend triple-checking your Gemfile.lock to see what other gems may be adding a capybara dependency where you're not expecting it.

@akshayrawat
Copy link

Same stacktrace after the upgrade. Don't have any other gems which depend on capybara.

@awead
Copy link

awead commented Nov 27, 2012

I ran into this problem too. Couldn't reproduce it, though. It went away after I emptied out my gemset and ran bundle install again.

@anthonator
Copy link

Same issue. xpath wasn't included as a dependency of capybara. Had to add xpath to my Gemfile manually in order to fix.

@DanielHeath
Copy link
Contributor

Same here, xpath not getting included.

@lock lock bot locked and limited conversation to collaborators Aug 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants