Graphql-engine: cli exits with "Killed: 9" (MacOS 11 aka Big Sur)

[bconnorwhite]

I'm assuming this issue is specific to the MacOS 11 beta- running the hasura cli downloaded from GitHub immediately exits with "Killed: 9".

If instead I clone the repo and build myself, the cli runs as normal.

[qpre]

Got the same issue using the latest beta of OXS Big Sur.

@bconnorwhite did you manage to get around this ?

[bconnorwhite]

There is either an issue in how the cli is built or in MacOS such that the cli only runs on MacOS 11 if it is built on MacOS 11. I'm not familiar with Go, so I was too lazy to debug the real issue myself.

This seems to work as a temporary solution though:

git clone https://github.com/hasura/graphql-engine
cd graphql-engine/cli
make deps
make build

Then use graphql-engine/cli/_output/master-xxxxxxxx-dirty/cli-hasura-darwin-amd64 to run.

[qpre]

Do you know when the Big Sur compatible prebuilt binaries will be available ?
Its release is pending and all Mac users upgrading will encounter this issue.

[coloradocolby]

Would really benefit from this being fixed as well!

[gusfune]

Same here using Big Sur 11.0.1 Beta (20B5012d), compiling from Go sources worked. Guess it's a matter of updating the binaries for this release.

[scriptonist]

Thanks for bringing this to notice folks, I think this was a problem with a tool we use to compress the binary. #6140 should probably have fix for this. It'll be great if someone can help us verify that the following build works fine.
https://200424-137724480-gh.circle-artifacts.com/0/cli/binaries/cli-hasura-darwin-amd64

[gusfune]

Thanks for bringing this to notice folks, I think this was a problem with a tool we use to compress the binary. #6140 should probably have fix for this. It'll great if someone can help us verify the following build works fine.
https://200424-137724480-gh.circle-artifacts.com/0/cli/binaries/cli-hasura-darwin-amd64

Yes, it worked nicely here @scriptonist.
OS: Big Sur 11.0.1 Beta (20B5012d)

[qpre]

Thanks for bringing this to notice folks, I think this was a problem with a tool we use to compress the binary. #6140 should probably have fix for this. It'll great if someone can help us verify the following build works fine.
https://200424-137724480-gh.circle-artifacts.com/0/cli/binaries/cli-hasura-darwin-amd64

Works for me too !

(also on 11.0.1 Beta (20B5012d))

[bubba]

Thanks for bringing this to notice folks, I think this was a problem with a tool we use to compress the binary. #6140 should probably have fix for this. It'll great if someone can help us verify the following build works fine.
https://200424-137724480-gh.circle-artifacts.com/0/cli/binaries/cli-hasura-darwin-amd64

Works for me too !

(also on 11.0.1 Beta (20B5012d))

Binary worked great for me too, thanks! Just had to chmod u+x and remove the quarantine flag before running:

$ xattr -d com.apple.quarantine /usr/local/bin/hasura

[Ciboulette]

Works great also 🦾 MacOS Big Sur 11.0.1 (20B29)

[alioguzhan]

Thanks for bringing this to notice folks, I think this was a problem with a tool we use to compress the binary. #6140 should probably have fix for this. It'll be great if someone can help us verify that the following build works fine.
https://200424-137724480-gh.circle-artifacts.com/0/cli/binaries/cli-hasura-darwin-amd64

I can confirm. that it works on 11.0.1 (20B29)

[wmhilton]

I upgraded to Big Sur last night 🙈. When will the fixed CLI be published on npm? I'm currently on "hasura-cli": "1.3.1".

Edit: I just realized the version on npm is not maintained by the core hasura team. But I think part of the point still stands, because I think this project needs to publish a 1.3.3 release before _that_ project can publish a 1.3.3 release.

[olegakbarov]

Works for me as well. Exact steps:

1. Download https://200424-137724480-gh.circle-artifacts.com/0/cli/binaries/cli-hasura-darwin-amd64
2. xattr -d com.apple.quarantine %downloaded file path%
3. mv %downloaded file path% /usr/local/bin/hasura
4. chmod u+x /usr/local/bin/hasura

[wmhilton]

For now I'm using @olegakbarov's instructions, modified to copy the file to node_modules/hasura-cli/hasura.

[olegakbarov]

I don't think issue should be closed, since there're only workarounds but not solution

[tirumaraiselvan]

@olegakbarov Github automatically closes issues when the corresponding PR is merged. This is also good for internal tracking. This has the unfortunate consequence that it feels like the fix is also released. I have added the milestone label for this so that it's clear about which version it will be released in.

[ryami333]

Hi there, upgraded to Big Sur and now I can't run a console for our Hasura application(s). Can we expect 1.3.3 to be released today?

[cakemountain]

Broken for me as well, upgraded to Big Sur last night. Similar error: [1] 23092 killed hasura

[cakemountain]

@olegakbarov do you happen to have a solution for yarn dependency management? Your solution above works great for running Hasura manually but fails on yarn commands with the same error, I'm assuming because yarn doesn't pull from the /usr/local/bin version your solution manually patches.

[toddheslin]

@cakemountain there was a new version released, which should fix the problem.

Uninstall the current version

Install again

I temporarily used the workaround last night but the newly released version 1.3.3 works fine.

[qpre]

works fine for me using Big Sur on Intel MBP 15" late 2018

[wmhilton]

Nice. The hasura-cli npm package has been updated to 1.3.3 too. So it all works now!