Open TheNotary opened 7 years ago
@TheNotary Rest assured, myself and a colleague are getting the same test failures that you are. We are currently looking into fixes for the heroku_set_spec. In regards to the "run_simple" command you mentioned, I am looking into that as well.
@TheNotary as an experiment, add this to ./lib/figaro/cli/heroku_set.rb
:
class HerokuSet < Task
def run
raise system('which heroku').to_s #add this line please
system(configuration, command)
end
On my end, the first path object is pointing to /usr/local/bin/heroku
. Based on the CommandInterceptor module, I think it should point to ./spec/support/bin/heroku
so the problem is that Aruba is either using a different environment where it can find the real heroku or it's caching the location.
I had to use raise
instead of a debugger like pry or byebug because Aruba is also running in a way where i can't interact with the debugger once we hit it.
I'm wondering if my system needs a little tweaking to get
run_simple
to work or if the tests are red for everyone because the tests are in an incomplete state.