You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run scripts/install.sh and then try to compose a supergraph, I get an error
➜ rover supergraph compose --elv2-license accept --skip-update --config examples/basic/supergraph.yaml
error: Output from `/Users/itme/.rover/bin/supergraph-v2.0.0-preview.10 compose` was malformed.
Caused by:
0: /Users/itme/.rover/bin/supergraph-v2.0.0-preview.10 compose output:
1: EOF while parsing a value at line 1 column 0
This error was unexpected! Please submit an issue with any relevant details about what you were trying to do: https://github.com/apollographql/rover/issues/new/choose
I can run the binary to get the version and it will tell me if I feed it an invalid YAML, but if once it gets to "real composition" I get an illegal hardware instruction
➜ ~/.rover/bin/supergraph-v2.0.0-preview.10 compose --version
supergraph-v2.0.0-preview.10-compose 2.0.0-preview.10
➜ ~/.rover/bin/supergraph-v2.0.0-preview.10 compose composition-tests/bonk.yaml
{"Err":{"build_errors":[{"message":"Config for subgraph(s) [\"other\"] are not fully resolved. name, routing_url, and sdl must be present.","code":null,"type":"config"}]}}
➜ ~/.rover/bin/supergraph-v2.0.0-preview.10 compose composition-tests/bare.yaml
[1] 36549 illegal hardware instruction ~/.rover/bin/supergraph-v2.0.0-preview.10 compose composition-tests/bare.yaml
NOTE: I've permanently disabled Gatekeeper by running sudo spctl --master-disable since we were investigating if it was related to apollographql/rover#398
The text was updated successfully, but these errors were encountered:
When I run
scripts/install.sh
and then try to compose a supergraph, I get an errorI can run the binary to get the version and it will tell me if I feed it an invalid YAML, but if once it gets to "real composition" I get an illegal hardware instruction
NOTE: I've permanently disabled Gatekeeper by running
sudo spctl --master-disable
since we were investigating if it was related to apollographql/rover#398The text was updated successfully, but these errors were encountered: