could this fail more gracefully?

pop a warning/confirmation if a user tries to do learn next from within their current lesson if they haven't yet completed it

will require some learn status work to be done first

right now, if a user hasn't set up with the osx app (and doesn't have a proper config entry in their .netrc), and they run learn, it prompts for their creds and then stops. it should then continue to run the test suite instead of requiring the user to run learn again.

Idea proposed by Logan. Potentially useful to make sure people will be on latest version, given importance of gem at the center of so much of what we're trying to co-ordinate. But seems like a pretty unprecedented move? Do other gems do this?

One option would be to check one per day upon user entering command, prompt user telling them there is a new version available upon entering next command (so the check can happen async)

@loganhasson other thoughts to add?

learn submit bananas

back up as is happening now

I opened a lesson using the gem, and it opened it in sublime. I then tried to continue working in terminal but was unable to proceed.

Not sure if this is because it never reached “done”, if I am doing something wrong, or if a step needs to be added. As a new student I wouldn’t know how to move forward other than restarting my terminal.

• am i in the directory of my current lesson? -> do current learn next behavior
• otherwise, just delegate to learn open

it should ONLY gsub and backup if a) a lesson b) remote org name is one of our org names (and not if the remote url has the org name in it anywhere)

Adds a Github issue, authored by this student on the repo of their current lab

Opens browser at current lesson

Syntax is learn submit [“message text”]

Logic is:

• In current directory & branch do:
• git add .
• git commit -m “message”
• git push
• Automatically opens a PR
• “message text” optional, if not supplied just default to “Done.”

when somebody types something like learn banana, it shouldn't blow up

the lab stilled opened and I still received a green light for opening it.

unsure if this is a problem here or with the os x app

syntax should be:

learn submit --team aviflombaum, maclover7

this would add the appropriate comment to the PR to tag team members avi and moss, and give them credit on learn (e.g. flip their lights)

@loganhasson @adamjonas

-_-

Ran learn, after a bit it failed, then it continued to run and gave me the error messages

Runs local test suite in current directory

learn should be alias for learn test

Make sure learn requires rspec 3 so that they 100% have rspec 3 installed.

Syntax is learn open [lab_name] [-editor <editor_name>]

Logic is:

If lab_name provided use that, else use current lesson. For this lab:

• Automatically fork it
• Automatically clone to working directly
• Automatically cd into directory
• If editor flag provided (or set in config file), then open working directory in editor

If lab is actually a README, just open Chrome at that lesson page

Note: --editor=sublime should be considered a default, written to a configuration file for all users that have set up through the OSX app. So that for these users, even if not supplying --editor, Sublime will open for them

• Injects a question relating to the current lab student is working on.
• Other students notified on Learn and via OSX app.

or get rid of flags (default subl -w breaks)

it should at least output the actual traceback. but should also try and hide the gem itself breaking

• Verifies student’s environment and reports any warnings or issues
• Offers user option (y/n) to automatically try to fix warnings/issues (e.g. download newer versions of stuff..)

sample backtrace:

 /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:923:in `connect': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (OpenSSL::SSL::SSLError)<br/>    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:923:in`block in connect'
    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb:74:in `timeout'<br/>    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:923:in`connect'
    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:863:in `do_start'<br/>    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:852:in`start'
    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:583:in `start'<br/>    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:478:in`get_response'
    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:455:in `get'<br/>    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/gems/learn-co-2.3.0/lib/learn/internet_connection.rb:35:in`block in test_connection'
    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb:89:in `block in timeout'<br/>    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb:34:in`block in catch'
    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb:34:in `catch'<br/>    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb:34:in`catch'
    from /Users/tadeanzalone/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/timeout.rb:104:in `timeout'<br/>    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/gems/learn-co-2.3.0/lib/learn/internet_connection.rb:34:in`test_connection'
    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/gems/learn-co-2.3.0/lib/learn/internet_connection.rb:29:in `initialize'<br/>    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/gems/learn-co-2.3.0/lib/learn/internet_connection.rb:14:in`new'
    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/gems/learn-co-2.3.0/lib/learn/internet_connection.rb:14:in `no_internet_connection?'<br/>    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/gems/learn-co-2.3.0/bin/learn:21:in`<top (required)>'
    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/bin/learn:23:in `load'<br/>    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/bin/learn:23:in`<main>'
    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'<br/>    from /Users/tadeanzalone/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in`<main>

Generates a new lab. Should list templates you can generate off. It’s difficult because you have to choose a language, and then a lab type and that’s tuff. We’d need to support templates the way the rails bin and really point to the git template you want.

shouldn't blow up the gem also (aka, should not see any gem errors in traceback):

get user confirmation - [Yn]

Lists out all supported commands with usage

should probably already work with learn test (maybe?). but need to figure out a good way of getting this to work.

List all tracks student can take with descriptions

ctrl+c does exactly nada.

Repro:

1. open terminal
2. cd into the directory where your lessons are saved
3. run learn open plus beginning of lab name and tab to complete the name
4. Hit enter
5. Result:

Looks like the auto-added / is causing the command to not find the lesson and open it.

• Changes student’s active track to trackname
• Automatically opens contents of student’s current lesson in that track in Sublime
• Pops open Chrome tab at lesson page

faraday connection error - in conjunction with the pre warning that now exists when a user doesn't have internet, need to rescue from faraday connection errors so that it doesn't throw an ugly error. can probably just do this in the learn-web gem

prints version of the learn CLI.

it tries to call match on nil

this error blows things up in the ios_lesson? method on line 160 (in learn-open)

'Not a valid Git repository' confuses people.

use a gem called 'liftoff'
https://github.com/learn-co-curriculum/ios-curriculum/tree/master/liftoff-templates

When a user clicks Submit on the Learn companion but their local build is the same as master, throw up an error message. Currently it looks like the PR is being submitted but then nothing happens.

In theory we could create a learn-console extension gem that provides a generic console that loads the environment.

task :console do
  require_all "./config" if Dir.exists?("./config")
  require_all "./app" if Dir.exists?("./app")
  require_all "./lib" if Dir.exists?("./lib")
  require_all "./*.rb" if Dir.entries(".").include?(/\.rb/)

  Pry.start
end

Given require_all gem, that code should work for all Ruby labs. If the lab defines it's own console task, we can use that, otherwise fallback to this default. In Rails labs, learn console could delegate to rails console.

so that .results.json doesn't get deleted (that way the osx app can piggy pack off of the learn-test gem and clean up the results file itself when it's done reading from it)

probably need to handle the --format flag like the -o and --out flags

Instructions to add Node and NPM in Terminal run:

$ brew install node

This should install both node and npm. This should be all that's required... I think Homebrew puts everything reachable within existing PATH.

If not, you can add node modules and and npm to your PATH in ~/.bash_profile like so:

export NODE_MODULES_PATH="/usr/local/share/npm/lib/node_modules"
export NPM_PATH="/usr/local/share/npm/bin"
export PATH="$POSTGRES_APP_PATH:$NEW_GIT_PATH:$USR_PATHS:$RVM_PATH:$PYTHON_SHARE:$PHP_PATH:$HEROKU_PATH:$NODE_MODULES_PATH:$NPM_PATH:$RABBIT_PATH:$PATH"

That's how mine looks anyway...
To test after install in Terminal run:

$ node -v
$ npm -v

These should return version numbers if it worked succesfully.

it can feel SUPER slow if there's no output before the actual submit/open/etc command output

• Moves user into the directory of their current lab
• Opens sublime with contents of that directory
• Pops open Chrome tab at lesson page

• Shows student current green light status for this lab
• Summary of # tests passing / failing
• Time since you started this lab
• # of other students working on this lab
• Average time taken by students that have completed this lab