This project is for the Heroku CLI only. Use https://help.heroku.com for anything that is not specific to the CLI itself.
bug
When running any Heroku command, I see:
› Warning: HEROKU_BINPATH set to /Users/<my username>/.local/share/heroku/client/bin/heroku
This changed in the last hour or so. I notice that v7.16.1 was just released https://github.com/heroku/cli/commit/393ef3bf599c12452004bf2b15dbd6d4c16be867 two hours ago.
$ heroku --version
› Warning: HEROKU_BINPATH set to /Users/<my username>/.local/share/heroku/client/bin/heroku
› Warning: HEROKU_BINPATH set to /Users/<my username>/.local/share/heroku/client/bin/heroku
heroku/7.16.1 darwin-x64 node-v10.10.0
Running heroku update doesn't change this, and I see the same output afterward.
Running with DEBUG=* as the issue template suggests, I see this:
$ heroku update DEBUG=*
› Warning: HEROKU_BINPATH set to /Users/<myusername>/.local/share/heroku/client/bin/heroku
heroku: Updating CLI... !
Error: HTTP Error 404 for GET https://cli-assets.heroku.com/channels/DEBUG=*/darwin-x64
<html>
<head><title>404 Not Found</title></head>
<body>
<h1>404 Not Found</h1>
<ul>
<li>Code: NoSuchKey</li>
<li>Message: The specified key does not exist.</li>
<li>Key: channels/DEBUG=*/darwin-x64</li>
<li>RequestId: 5CC528D5A766481C</li>
<li>HostId: +AfL/OXHN9Mv8jJq/nWywAlsOkFjM10jzxLHNtszF+upNkWHjbcmcwASxIF3h2+tuU3gKnxV5bA=</li>
</ul>
<hr/>
</body>
</html>
at HTTP._request (~/.local/share/heroku/client/7.16.1/node_modules/http-call/lib/http.js:214:19)
I'm expecting it to run the command without warnings. I grepped through heroku/cli to see if I could see where this env variable is coming from (https://github.com/heroku/cli/search?q=HEROKU_BINPATH&type=Code) and also searched online but didn't see anything that jumped out or might be helpful.
Please mention your heroku and OS version. Please state if you are behind an HTTP proxy or company firewall as well.
Mac, El Capitan 10.11.6. I was initially behind a firewall but have never run into this problem on that network before. The 404 error above suggests maybe it's related to a firewall, but I can't understand how that would be related to the ENV variable value mentioned in this warning. To debug, I connected to another network without the same firewall rules, and still see the same warning.
Thanks!
Thanks for the reporting this. Should have a fix in master soon.
Most helpful comment
Thanks for the reporting this. Should have a fix in master soon.