On Sun, Oct 4, 2015 at 10:04 AM, John D. Ament <[email protected]> wrote: > I got a bit further. I gave up on my mac, and spun my linux workstation > back up. That was fun.
Thanks for your perseverance! > Anyways, I got everything running, however anytime I would access > localhost:9292, I'd get a stacktrace on this line > > https://github.com/rubys/whimsy-agenda/blob/master/routes.rb#L62 > > For some reason, ASF::Person.find(id).public_name was returning Nilvalue. > I still have to figure out which ID was causing this. I replaced the line > with > > [initials, id] > > And then I had the board agenda tool running. Do me a favor, Then visit the page in your browser, view source, and search for Directors. Then change the line to add a to_s (to String) call thus: [initials, ASF::Person.find(id).public_name.to_s.split(' ').first] Do it again, and tell me what you got each time. Here is what I see: directors: { rb: "Rich", sc: "Shane", bd: "Bertrand", jj: "Jim", cm: "Chris", dn: "David", bp: "Brett", sr: "Sam", gs: "Greg" } Alternately, you can use your javascript console to examine: Server.directors Additionally, you can try explore using irb (interactive Ruby): $ irb -r whimsy/asf irb(main):001:0> ASF::Person.find('rubys').public_name => "Sam Ruby" > John - Sam Ruby > On Fri, Oct 2, 2015 at 9:11 PM Sam Ruby <[email protected]> wrote: > >> On Fri, Oct 2, 2015 at 8:50 PM, John D. Ament <[email protected]> >> wrote: >> > sudo seems to be the issue. Tried again without sudo, that was better. >> >> OK, zapped from the README. Thanks! >> >> > Now i'm stuck on rake spec. It just runs. No output. I would imagine >> > theres output. >> >> Here's some things to try/compare against: >> >> $ rake clobber >> rm -rf test/work >> >> $ rake test:setup >> rm -rf test/work/repository >> mkdir -p test/work >> Checked out revision 0. >> cp ../data/board_minutes_2015_01_21.txt >> ../data/board_agenda_2015_02_18.txt >> ../data/board_agenda_2015_01_21.txt board >> A board_agenda_2015_01_21.txt >> A board_agenda_2015_02_18.txt >> A board_minutes_2015_01_21.txt >> Adding board_agenda_2015_01_21.txt >> Adding board_agenda_2015_02_18.txt >> Adding board_minutes_2015_01_21.txt >> Transmitting file data ... >> Committed revision 1. >> mkdir -p test/work/data >> cp test/board_minutes_2015_01_21.yml >> test/work/data/board_minutes_2015_01_21.yml >> cp test/board_minutes_2015_02_18.yml >> test/work/data/board_minutes_2015_02_18.yml >> cp test/test.yml test/work/data/test.yml >> >> $ rake spec --trace >> ** Invoke spec (first_time) >> ** Invoke test:setup (first_time) >> ** Invoke reset (first_time) >> ** Execute reset >> ** Invoke work (first_time) >> ** Invoke test/work/board (first_time, not_needed) >> ** Invoke test/work/repository (first_time) >> ** Invoke test/work (first_time, not_needed) >> ** Execute test/work/repository >> ** Invoke test/work/data/board_minutes_2015_01_21.yml (first_time, >> not_needed) >> ** Invoke test/work/data/board_minutes_2015_02_18.yml (first_time, >> not_needed) >> ** Invoke test/work/data/test.yml (first_time, not_needed) >> ** Execute work >> ** Execute test:setup >> ** Execute spec >> /usr/bin/ruby2.2 >> >> -I/var/lib/gems/2.2.0/gems/rspec-support-3.3.0/lib:/var/lib/gems/2.2.0/gems/rspec-core-3.3.2/lib >> /var/lib/gems/2.2.0/gems/rspec-core-3.3.2/exe/rspec --pattern >> spec/\*\*\{,/\*/\*\*\}/\*_spec.rb >> ........................................................... >> >> Finished in 39.13 seconds (files took 1.41 seconds to load) >> 59 examples, 0 failures >> >> >> If all else fails, try control-C to stop the rake task, and see if you >> get a stack traceback. >> >> > Everything seems to be going against 2.2.1. >> > >> > Johns-MBP-2:whimsy-agenda johnament$ which ruby >> > >> > /Users/johnament/.rbenv/shims/ruby >> > >> > Johns-MBP-2:whimsy-agenda johnament$ which bundle >> > >> > /usr/bin/bundle >> > >> > There is no ~/.rbenv/shims/bundle FWIW. >> >> While I know quite a few Mac OS/X users who swear by rbenv, my >> experience is that it presumes a bit more knowledge about how things >> work than alternatives. You may need to run a command like `rbenv >> rehash` or `bundle install --binstubs`. >> >> https://github.com/sstephenson/rbenv#understanding-shims >> >> https://github.com/sstephenson/rbenv/wiki/Understanding-binstubs#bundler-generated-binstubs >> >> - Sam Ruby >> >> > On Fri, Oct 2, 2015 at 8:13 PM Sam Ruby <[email protected]> wrote: >> > >> >> On Fri, Oct 2, 2015 at 7:43 PM, John D. Ament <[email protected]> >> >> wrote: >> >> > I followed the Direct steps verbatim (copy and pasted). >> >> >> >> OK, the problem might have been the sudo then. >> >> >> >> I see that you are using rbenv, presumably to manage a separate >> >> installation of Ruby. Perhaps "bundle install" installed the >> >> necessary gems for the system version of Ruby (presumably 2.0?) >> >> instead of the rbenv version (2.2.1). >> >> >> >> It is also possible that you would have needed to run `rbenv rehash` >> >> or installed the gem-rehash plugin to generate the necessary shim. >> >> >> >> Can I get you to run `which ruby' and `which bundle`? If the paths >> >> differ, try `gem install bundler` (without the sudo) and run `which >> >> bundle` again. >> >> >> >> > John >> >> >> >> - Sam Ruby >> >> >> >> > On Fri, Oct 2, 2015 at 7:28 PM Sam Ruby <[email protected]> >> wrote: >> >> > >> >> >> On Fri, Oct 2, 2015 at 7:24 PM, John D. Ament <[email protected] >> > >> >> >> wrote: >> >> >> > It seems I needed the following dependencies installed, via gem >> >> install >> >> >> > >> >> >> > whimsy-asf >> >> >> > rspec >> >> >> > capybara >> >> >> > sinatra >> >> >> >> >> >> By any chance did you skip the following steps? >> >> >> >> >> >> gem install bundler >> >> >> bundle install >> >> >> >> >> >> What the second step will do is install all of the gems mentioned in >> >> >> the following: >> >> >> >> >> >> https://github.com/rubys/whimsy-agenda/blob/master/Gemfile >> >> >> >> >> >> - Sam Ruby >> >> >> >> >> >> > On Fri, Oct 2, 2015 at 7:04 PM John D. Ament < >> [email protected]> >> >> >> wrote: >> >> >> > >> >> >> >> I just tried the direct option. Stopped at rake spec >> >> >> >> >> >> >> >> Johns-MBP-2:whimsy-agenda johnament$ rake spec --trace >> >> >> >> >> >> >> >> rake aborted! >> >> >> >> >> >> >> >> LoadError: cannot load such file -- whimsy/asf/config >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in >> >> >> >> `require' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in >> >> >> >> `require' >> >> >> >> >> >> >> >> /Users/johnament/src/whimsy-agenda/Rakefile:1:in `<top >> (required)>' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/rake_module.rb:28:in >> >> >> >> `load' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/rake_module.rb:28:in >> >> >> >> `load_rakefile' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:689:in >> >> >> >> `raw_load_rakefile' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:94:in >> >> >> >> `block in load_rakefile' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:176:in >> >> >> >> `standard_exception_handling' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:93:in >> >> >> >> `load_rakefile' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:77:in >> >> >> >> `block in run' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:176:in >> >> >> >> `standard_exception_handling' >> >> >> >> >> >> >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:75:in >> >> >> >> `run' >> >> >> >> >> >> >> >> /Users/johnament/.rbenv/versions/2.2.1/bin/rake:33:in `<main>' >> >> >> >> >> >> >> >> >> >> >> >> Any thoughts? >> >> >> >> >> >> >> >> >> >> >> >> John >> >> >> >> >> >> >> >> On Fri, Oct 2, 2015 at 2:19 PM Sam Ruby <[email protected]> >> >> wrote: >> >> >> >> >> >> >> >>> On Thu, Oct 1, 2015 at 4:21 PM, Marvin Humphrey < >> >> >> [email protected]> >> >> >> >>> wrote: >> >> >> >>> > >> >> >> >>> > I'm "stuck" at `gem install whimsy-asf`. Ruby comes with my >> >> >> operating >> >> >> >>> system. >> >> >> >>> > I don't want to mess with the system installation, which meeds >> >> that I >> >> >> >>> need to >> >> >> >>> > research how to persuade the `gem` tool to install into an >> >> arbitrary >> >> >> lib >> >> >> >>> > directory, then modify some environment var so that ruby knows >> >> about >> >> >> the >> >> >> >>> > custom lib directory, etc. >> >> >> >>> >> >> >> >>> I've now done the research. >> >> >> >>> >> >> >> >>> How to persuade the `gem` tool to install into an arbitrary lib >> >> >> directory: >> >> >> >>> >> >> >> >>> $ export GEM_HOME=/arbitrary/lib/directory >> >> >> >>> >> >> >> >>> How to modify some environment var so that ruby knows about the >> >> custom >> >> >> >>> lib directory: >> >> >> >>> >> >> >> >>> $ export GEM_PATH=/arbitrary/lib/directory >> >> >> >>> >> >> >> >>> With these two environment variables set, and presuming that you >> >> have >> >> >> >>> configure LDAP, you should be able to: >> >> >> >>> >> >> >> >>> gem install whimsy-asf >> >> >> >>> ruby examples/board.rb --port=9292 >> >> >> >>> >> >> >> >>> When you are done, feel free to rm -rf >> /arbitrary/lib/directory. Or >> >> >> >>> keep it around for future use. Note that sudo is not required >> and >> >> >> >>> your system configuration is not messed with. >> >> >> >>> >> >> >> >>> Notes: >> >> >> >>> >> >> >> >>> 1) GEM_PATH is actually a path, so you can specify multiple paths >> >> >> >>> separated by colons and each will be searched in order. You can >> use >> >> >> >>> the command 'gem env' to see your current path. If you unset >> >> >> >>> GEM_PATH, you will likely see an entry like the following: >> >> >> >>> /Users/rubys/.gem/ruby/2.0.0. >> >> >> >>> >> >> >> >>> 2) gem install will install all necessary dependencies for a >> single >> >> >> >>> gem. Applications that make use of multiple gems typically >> provide >> >> a >> >> >> >>> file name `Gemfile` that lists the versions of the gems that the >> >> >> >>> application depends on, and a command `bundle install` is >> sufficient >> >> >> >>> to download all necessary dependencies. >> >> >> >>> >> >> >> >>> 3) I haven't done the research for node/npm, but running "npm >> config >> >> >> >>> ls -l" leads me to believe that npm is equally as configurable. >> >> >> >>> >> >> >> >>> > I, and other potential contributors, can surely figure all this >> >> out >> >> >> in >> >> >> >>> due >> >> >> >>> > time -- but I don't think we should have to. And I feel as >> though >> >> >> if I >> >> >> >>> > compromise with you now, guzzle the kool-aid and spend N hours >> >> >> tricking >> >> >> >>> out my >> >> >> >>> > system, that my point about all these dependencies posing a >> >> barrier >> >> >> to >> >> >> >>> entry >> >> >> >>> > will be lost. >> >> >> >>> >> >> >> >>> My personal preference is NOT to try to "trick out my system", >> but >> >> >> >>> rather to use the tools as others on sites like stackoverflow do. >> >> >> >>> Generally, I've found that this increases the odds that >> solutions I >> >> >> >>> find there work for me. >> >> >> >>> >> >> >> >>> In cases where I desire additional isolation, I look to running >> a VM >> >> >> >>> or a Docker container. >> >> >> >>> >> >> >> >>> > Marvin Humphrey >> >> >> >>> >> >> >> >>> - Sam Ruby >> >> >> >>> >> >> >> >> >> >> >> >> >> >>
