Lab folder has 2 files named my_all.rb (one inside the lib subfolder and one in the root folder), one of which contains the solution.

On Cloud9 when running the learn command it would get stuck so I would have to ctrl-c out of it. The errors I received were as follows. This occurred when I commented out the code as well so there were no syntax issues.

// ♥ learn
^C/usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/resolver/api_specification.rb:8:in <top (required)>': Interrupt from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:122:in require'
from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:122:in require' from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/resolver.rb:342:in <top (required)>'
from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:122:in require' from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:122:in require'
from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems/request_set.rb:397:in resolve_current' from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems.rb:245:in finish_resolve'
from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems.rb:313:in block in activate_bin_path' from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems.rb:311:in synchronize'
from /usr/local/rvm/rubies/ruby-2.3.3/lib/ruby/site_ruby/2.3.0/rubygems.rb:311:in activate_bin_path' from /usr/local/rvm/gems/ruby-2.3.3/bin/learn-test:23:in

I ended up playing with it in my local ubuntu environment on atom and got different errors when I ran the tests:

I ended up figuring out that if I commented out the

require 'pry'

at the top of the my_all.rb that I could run the tests via 'rspec' but running them via 'learn' was still broken.

I don't know if it is a me issue or a lab issue let me know if there is any other information you need I can probably replicate the issue.