-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wgc commands are failing #592
Comments
WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. |
I think this might be the same issue as #582. Please makes sure you're using Node 18+. |
Hi, if you are self hosting the controlplane as well, you should see relevant errors there. Please send that as well, else it is difficult to debug. Thank you. |
@ricardogoncalvesmindera what are the outputs of "which wgc" and "which node"? |
I found out the issue, the create subgraph command is missing the label option, if i add the --label env=qa the command work. I didn't know it was mandatory. |
You can close it as non-issue. Thank you and sorry for the time you spent. |
It is no longer necessary to include labels in federated graphs or subgraphs. However, if your federated graph was already created with labels, its constituent subgraphs must match that label. But please also note that if you choose not to use labels, all federated graphs within that namespace will be composed with the same (unlabeled) subgraphs. The only difference between the federated graphs will be the routing URL. Sorry for the confusion. |
Hi @ricardogoncalvesmindera. Seems you are not on the latest version of the control plane (although in the issue you have specified it as so) but your CLI is. Please upgrade so you don't face compatibility issues like these and take care to specify the correct version in the issue. |
Component(s)
cli
Component version
latest
wgc version
latest
controlplane version
latest
router version
latest
What happened?
Since a few days ago i'm not able to run any wgc commands, i get the following error:
/app # wgc federated-graph update qa --label-matcher env=qa --routing-url https://graphql-qa.com/cosmo/v1/graphql ConnectError: [internal] internal error at errorFromJson (file:///usr/local/lib/node_modules/wgc/node_modules/@connectrpc/connect/dist/esm/protocol-connect/error-json.js:54:19) at errorFromJsonBytes (file:///usr/local/lib/node_modules/wgc/node_modules/@connectrpc/connect/dist/esm/protocol-connect/error-json.js:93:12) at next (file:///usr/local/lib/node_modules/wgc/node_modules/@connectrpc/connect/dist/esm/protocol-connect/transport.js:113:31) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.unary (file:///usr/local/lib/node_modules/wgc/node_modules/@connectrpc/connect/dist/esm/protocol-connect/transport.js:63:20) at async Object.updateFederatedGraph (file:///usr/local/lib/node_modules/wgc/node_modules/@connectrpc/connect/dist/esm/promise-client.js:67:26) at async Command.<anonymous> (file:///usr/local/lib/node_modules/wgc/dist/commands/federated-graph/commands/update.js:27:22) at async Command.parseAsync (/usr/local/lib/node_modules/wgc/node_modules/commander/lib/command.js:936:5) at async file:///usr/local/lib/node_modules/wgc/dist/index.js:8:5 { rawMessage: 'internal error', code: 13, metadata: HeadersList { cookies: null, [Symbol(headers map)]: Map(8) { 'access-control-allow-credentials' => [Object], 'access-control-expose-headers' => [Object], 'connection' => [Object], 'content-length' => [Object], 'content-type' => [Object], 'date' => [Object], 'keep-alive' => [Object], 'vary' => [Object] }, [Symbol(headers map sorted)]: null }, details: [], cause: undefined }
This happens in the cosmo running in our infrastructure and also on cosmo running from the example locally.
Environment information
No response
Router configuration
No response
Router execution config
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: