You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 22, 2023. It is now read-only.
I'm using rvm on OSX Lion. I use a very simple bash script that runs a consular termfile, and I frequently encounter a NoMethodError in consular/osx.rb the first time I attempt to run this bash script. If I run the bash script a second time, then things proceed normally, which leads me to believe there is some kind of race condition in setting up the Ruby environment, possibly related to rvm.
What's tricky is that I never have any issues running other Ruby scripts via rvm...I've only ever seen this when running a consular script after boot-up.
I don't think it's the cause of any issues, but the bash script I use looks like this:
#!/bin/bash
RAILSBOX_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
cd $RAILSBOX_DIR && RAILSBOX_DIR=$RAILSBOX_DIR consular start
The subsequent Ruby error and callstack is as follows:
/Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:161:in `execute_command': undefined method `do_script' for nil:NilClass (NoMethodError)
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:110:in `block (2 levels) in execute_window'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:110:in `each'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:110:in `block in execute_window'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:95:in `each'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:95:in `execute_window'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:63:in `block in process!'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:63:in `each_pair'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-osx-1.0.1/lib/consular/osx.rb:63:in `process!'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-1.0.2/lib/consular/cli.rb:35:in `block in start'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-1.0.2/lib/consular/cli.rb:255:in `call'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-1.0.2/lib/consular/cli.rb:255:in `message_unless_file'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-1.0.2/lib/consular/cli.rb:35:in `start'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/thor-0.15.2/lib/thor/task.rb:27:in `run'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/thor-0.15.2/lib/thor/invocation.rb:120:in `invoke_task'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/thor-0.15.2/lib/thor.rb:275:in `dispatch'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/thor-0.15.2/lib/thor/base.rb:408:in `start'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/gems/consular-1.0.2/bin/consular:13:in `<top (required)>'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/bin/consular:19:in `load'
from /Users/jeffomatic/.rvm/gems/ruby-1.9.2-p290/bin/consular:19:in `<main>'
The text was updated successfully, but these errors were encountered:
/Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-osx-1.0.1/lib/consular/osx.rb:161:in `execute_command': undefined method `do_script' for nil:NilClass (NoMethodError) from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-osx-1.0.1/lib/consular/osx.rb:110:in `block (2 levels) in execute_window'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-osx-1.0.1/lib/consular/osx.rb:110:in `each'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-osx-1.0.1/lib/consular/osx.rb:110:in `block in execute_window'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-osx-1.0.1/lib/consular/osx.rb:95:in `each'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-osx-1.0.1/lib/consular/osx.rb:95:in `execute_window'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-osx-1.0.1/lib/consular/osx.rb:62:in `process!'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-1.0.2/lib/consular/cli.rb:35:in `block in start'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-1.0.2/lib/consular/cli.rb:255:in `call'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-1.0.2/lib/consular/cli.rb:255:in `message_unless_file'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-1.0.2/lib/consular/cli.rb:35:in `start'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/thor-0.18.0/lib/thor/command.rb:27:in `run'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/thor-0.18.0/lib/thor/invocation.rb:120:in `invoke_command'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/thor-0.18.0/lib/thor.rb:363:in `dispatch'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/thor-0.18.0/lib/thor/base.rb:427:in `start'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/gems/consular-1.0.2/bin/consular:13:in `<top (required)>'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/bin/consular:19:in `load'
from /Users/juergen/.rvm/gems/ruby-1.9.3-p194@xeer/bin/consular:19:in `<main>'
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using rvm on OSX Lion. I use a very simple bash script that runs a consular termfile, and I frequently encounter a NoMethodError in
consular/osx.rb
the first time I attempt to run this bash script. If I run the bash script a second time, then things proceed normally, which leads me to believe there is some kind of race condition in setting up the Ruby environment, possibly related to rvm.What's tricky is that I never have any issues running other Ruby scripts via rvm...I've only ever seen this when running a consular script after boot-up.
I don't think it's the cause of any issues, but the bash script I use looks like this:
The subsequent Ruby error and callstack is as follows:
The text was updated successfully, but these errors were encountered: