Evan Lucas

Is there a test you can add for this?

@jjviscomi The tests are. That is where I'm a little confused. Do you have an example of where this actually fails?

What node version are you running?

hm, mind trying with the latest node (v4.x). It tends to have better error messages.

interesting...can you try running with the `--loglevel silly` flag?

I think I would prefer something more like: ``` js var sh = '/bin/bash' var flag = '-c' if (process.platform === 'win32') { sh = process.env.comspec || 'cmd' flag =...

Yea, I'd be fine with that

Thanks for the contribution! Can you please explain the change and why it is needed? Thanks!

I'm not really sure that this is an issue in gcr. It looks to be more of an issue with gitlab-ci? Is it sending incorrect data to trigger the 500...

It may make sense to just make the three different types of inputs (sha, url, file) require a different flag for each one. It would definitely make it less ambiguous.