Bug #5134
open
[SDKs] CLI tools fail or warn when current working directory is gone
0%
Description
arv keep docker --no-pull bcosc/all-tools
/usr/local/rvm/gems/ruby-2.1.5@global/gems/rubygems-bundler-1.4.4/lib/rubygems-bundler/noexec.rb:5:in `pwd': No such file or directory - getcwd (Errno::ENOENT)
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/rubygems-bundler-1.4.4/lib/rubygems-bundler/noexec.rb:5:in `<class:Noexec>'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/rubygems-bundler-1.4.4/lib/rubygems-bundler/noexec.rb:3:in `<top (required)>'
from /usr/local/rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:128:in `require'
from /usr/local/rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
from /usr/local/rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:39:in `require'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/rubygems-bundler-1.4.4/lib/rubygems_executable_plugin.rb:4:in `block in <top (required)>'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/executable-hooks-1.3.2/lib/executable-hooks/hooks.rb:50:in `call'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/executable-hooks-1.3.2/lib/executable-hooks/hooks.rb:50:in `block in run'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/executable-hooks-1.3.2/lib/executable-hooks/hooks.rb:49:in `each'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/executable-hooks-1.3.2/lib/executable-hooks/hooks.rb:49:in `run'
from /usr/local/rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:10:in `<main>'
Updated by Brett Smith almost 10 years ago
- Subject changed from arv keep docker fails with bcosc/all-tools to [SDKs] CLI tools fail or warn when current working directory is gone
- Category set to SDKs
- Target version set to Bug Triage
From IRC follow-up:
- Calling
arv-keepdockerdirectly produced the warningsh: 0: getcwd() failed: No such file or directory, but ultimately succeeded. - Bryan was in a directory that no longer existed. The commands worked fine after a
cd.
A lot of our tools don't need to work in the current directory in principle, but I'm not sure how much effort it's worth to make sure that's a reality, especially since the issues are apparently in underlying tools. The exception displayed here seems to come from Bundler. The Python warning might be a little easier to address; it happens as soon as you import arvados, so it's apparently something happening in a module top level.
Updated by Tom Clegg almost 10 years ago
- Target version changed from Bug Triage to Arvados Future Sprints
Updated by Ward Vandewege over 3 years ago
- Target version deleted (
Arvados Future Sprints)