Closed bradyaturner closed 10 years ago
@bobbyduhbrain
Update:
I'm not sure what happened last night, but the output after I reverted it isn't as confusing:
bradysmacbookpro:rubyhue bradyaturner$ git diff
diff --git a/lib/rubyhue.rb b/lib/rubyhue.rb
index 11c3581..a17a36a 100755
--- a/lib/rubyhue.rb
+++ b/lib/rubyhue.rb
@@ -65,6 +65,7 @@ class Hue
end
def request_bulb_info( id )
+ puts "TEST"
response = hue_get "lights/#{id}"
HueBulb.new(id,response)
end
bradysmacbookpro:rubyhue bradyaturner$ ./bin/hue list
TEST
[1] Hue Lamp 1
TEST
[2] Hue Lamp 2
TEST
[3] Hue Lamp 3
TEST
[4] Hue Lamp 4
TEST
[5] BT Lamp
bradysmacbookpro:rubyhue bradyaturner$ hue list
TEST
[1] Hue Lamp 1
TEST
[2] Hue Lamp 2
TEST
[3] Hue Lamp 3
TEST
[4] Hue Lamp 4
TEST
[5] BT Lamp
bradysmacbookpro:rubyhue bradyaturner$ cd
bradysmacbookpro:~ bradyaturner$ hue list
TEST
[1] Hue Lamp 1
TEST
[2] Hue Lamp 2
TEST
[3] Hue Lamp 3
TEST
[4] Hue Lamp 4
TEST
[5] BT Lamp
The installed and development CLI are both picking up changes to the dev code, but at least its consistent, and it works outside the project directory.
Closing this. Reverting the commit fixed the problem. We're still left with the executable problem, but I think we'll just have to live with "bundle exec hue" for now.
Changes do development code are being picked up by the installed executable:
And that's if you're running in the project directory. Anywhere else, and it just doesn't work:
I went back and checked out commit 8c9ea90795f0968dc2173c7d9fb71faea410cfac, before we merged #24, and now the executable works outside the project directory, but the behavior is weird:
In that output, the installed gem is picking up the change to the dev code, but the dev CLI isn't! WTF!