Autoupdated client crashes on Mac OS X El Capitan

[vic-cw]

Do you want to request a feature or report a bug?

bug

What is the current behavior?

Run heroku version. It will crash with following message:

dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin
  Referenced from: /Users/.../.local/share/heroku/client/10.0.0-b084308/bin/node
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: ____chkstk_darwin
  Referenced from: /Users/.../.local/share/heroku/client/10.0.0-b084308/bin/node
  Expected in: /usr/lib/libSystem.B.dylib

/Users/.../.local/share/heroku/client/bin/../10.0.0-b084308/bin/heroku: line 45: 48524 Trace/BPT trap: 5       "$NODE" "$DIR/run" "$@"

What is the expected behavior?

Should print version and exit.

I wouldn't be surprised if I receive a reply saying that El Capitan isn't supported.

However, I would argue that this is an autoupdated binary. I didn't do anything special since I first installed the command line interface, and this morning it broke. Thus if El Capitan is not supported, then the update should not happen. Instead, the executable should keep working, and optionally display a message saying it is out of date but unable to update because OS is not supported.

Another way to say it is that I have had to hack my way back to an older version, patch oclif plugin-update code to make sure it doesn't update again, and keep working. I shouldn't have to do that.

OS version Mac OS X 10.11.6, Heroku was autoupdated to 10.0.0 apparently.

[k80bowman]

@vic-cw thank you for letting us know about this issue. I looked into this and it most likely has to do with the Node version required. With the v10 release we moved the CLI to Node 20, which it looks like it supports Mac OS X 10.15 and above. If you want to install a version of the CLI that should not autoupdate, you can always install the v9.5.1 version using npm by running npm install -g [email protected].

[vic-cw]

@k80bowman thanks for the reply Katy.

Unfortunately it seems that my intent didn't go through.

I already achieved a way to not have the CLI auto update.

Through this issue I am saying that the CLI should not upgrade to a version that is not supported on the current system. Since it does, it means one can go through the terrible experience that I went through at any time: suddenly the CLI stops working, without any warning, and one has to find a way to downgrade.

[k80bowman]

@vic-cw Thank you, we appreciate the feedback.

[vic-cw]

@k80bowman you're welcome. So you don't plan on fixing this?

[k80bowman]

@vic-cw I left the issue open because I've brought the issue to our team. We're discussing how best to address it.