Boggs - 6/21/2016

[b-ggs]

Date: (6/21/2016)

What I Did and Worked On (Yesterday):

• Worked on adding options for group and source for bundle add. Dug through the codebase and found that Dependency, the class Injector uses, actually takes group and source as options, so that makes it easier to pass the needed options to the Gemfile.

  What I Will Do (Today):

• Continue working on adding options for group and source for bundle add
• Issue re: laduradura gem on different platforms
• Assign additional stories

  Any Blockers:

• An issue I've been having with pry-byebug detailed in the section below. I've been trying to recreate the laduradura manually to no avail.

  Interestings/Helps:

• bundler
  • How do you open up a pry session when running rspec tests? I've tried putting require "pry-byebug" inside spec/commands/outdated_spec.rb, spec/spec_helper.rb, and lib/bundler/cli/outdated.rb. I can open a session if I put binding.pry in outdated_spec.rb, but I haven't successfully opened up a session if I put it inside outdated.rb. What I would usually do is just recreate the test case with a real Gemfile and stuff, but I can't seem to recreate the test case manually this time around, so I'm relying heavily on the test case given in the issue report.

[RochesterinNYC]

@b-ggs for the integration specs, the bundle ~~~ invocation runs in a separate process so you can't access the binding.pry/debugging session in that other process from the primary process (the one running the specs). What I typically do is put a large sleep right before the bundle invocation in the appropriate spec, and then treat the generated tmp directory and its contents as a reproducible scenario you can copy, run bundle commands on, etc.

[b-ggs]

@RochesterinNYC Ah, I see. Didn't occur to me to use the generated tmp dir, ha. Just tried it out, works perfectly. Thanks!