-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
k/bugSomething isn't workingSomething isn't workingp/highcandidate for being included in the upcoming sprintcandidate for being included in the upcoming sprint
Description
Hello team,
First of all, thank for your amazing solution ! More than one year in production with happy users and no problem. 🤩
I have an issue with the remote schema feature. The server version is the 2.0.1. Let's take invocing_by_pk query from my remote schema.
If I run :
{
invoice_by_pk(id: "1398") {
id
}
}
The Hasura server fails by returning this error :
{
"errors": [
{
"extensions": {
"path": "$",
"code": "remote-schema-error"
},
"message": "Received invalid JSON value from remote"
}
]
}
The remote response is :
{
"data": {
"invoice_by_pk": {
"id": "1398"
}
},
"extensions": {
"tracing": {
"version": 1,
"startTime": "2021-06-28T16:08:35.924Z",
"endTime": "2021-06-28T16:08:36.222Z",
"duration": 298583777,
"execution": {
"resolvers": [
{
"path": [
"invoice_by_pk"
],
"parentType": "Query",
"fieldName": "invoice_by_pk",
"returnType": "invoice",
"startOffset": 3560552,
"duration": 294694932
},
{
"path": [
"invoice_by_pk",
"id"
],
"parentType": "invoice",
"fieldName": "id",
"returnType": "String!",
"startOffset": 298360006,
"duration": 54232
}
]
}
}
}
}
If I disable the tracing extension from my remote schema server (Apollo), the call succeeds.
However, I noticed extensions works when I run the query from a nested Hasura field like that :
{
user(where: {invoicingId: { _eq: "1398"} }) {
invoice {
id
}
}
}
```
Hope it can help.
Yoann
AssafKr, yogevlahyani, BenoitRanque, andrewmcoupe, jovermier and 3 more
Metadata
Metadata
Assignees
Labels
k/bugSomething isn't workingSomething isn't workingp/highcandidate for being included in the upcoming sprintcandidate for being included in the upcoming sprint