drk
02/19/2018, 11:59 PMError: Cannot use GraphQLSchema "[object Object]" from another module or realm.
when running yarn dev
using the advanced typescript template?drk
02/19/2018, 11:59 PMaeblin
02/20/2018, 12:05 AMgraphql-tag is not listed in the project's dependencies.
Since graphql-tag is bundled in graphql-yoga, I know it’s available. How do I make that clear to ESLint?alx
02/20/2018, 1:10 AMgraphql-cli
? The graphql validate function seems to want it in this format: https://github.com/graphql/graphql-js/blob/master/src/validation/__tests__/harness.js#L329. Is there some type of parser or loader I can use? Or is there an easier way to validate a query? Thanks!niwat
02/20/2018, 2:58 AMnick
02/20/2018, 4:50 AMuser
02/20/2018, 6:28 AMhttps://prisma.slack.com/files/U9BJ1J810/F9BMM5U3F/graphcool_clone.png▾
eddig
02/20/2018, 6:56 AMmap
function and believe that cover all, but we still have this error. Would be cool to have at least the event
in addition to error
for testing it inside the function. But if in the error will be the meaningful line number that points to the place in our function where the error appears it would be amazing! 🤩
The question, is any chance of having this changes in the Legacy Console project, or we need to migrate to the Graphcool Framework? Is in the Graphcool Framework we will have more helpful tools for figuring out where the problems in our functions?
Thanks for your work!sixtatami
02/20/2018, 9:38 AMsixtatami
02/20/2018, 9:52 AMsixtatami
02/20/2018, 9:52 AMprisma-eu1
)
HTTP: https://eu1.prisma.sh/wisy-6/dev
Websocket: https://eu1.prisma.sh/wisy-6/devsixtatami
02/20/2018, 9:54 AMlawrence
02/20/2018, 11:37 AMprisma deploy
- is there something I’m missing when removing data types?tomhut
02/20/2018, 11:53 AMnoahdavis
02/20/2018, 12:33 PM{
"data": {
"signup": null
},
"errors": [
{
"message": "Field \"user\" of type \"User\" must have a selection of subfields. Did you mean \"user { ... }\"?",
"locations": [
{
"line": 3,
"column": 3
}
],
"path": [
"signup"
]
}
]
}
^ just started happening, doesn't matter if we are using the prisma cloud deployed data store (AWS Aurora) or the public clustersnoahdavis
02/20/2018, 12:34 PMeddig
02/20/2018, 12:39 PMzonofthor
02/20/2018, 1:07 PMeddig
02/20/2018, 1:34 PMProfile
and few subscriptions to create/update this type of node. When we test creating the profile via playground in the legacy graphcool console <https://console.graph.cool/_project_/playground>
(https://monosnap.com/file/hCt94k7a3EqqaOsVLqwfgX0K4HEhlk) the subscription function works as expected without errors in the logs, but when we try to create the profile via our endpoint’s playground <https://api.graph.cool/relay/v1/_project_>
(https://monosnap.com/file/kSZ5okqqO2of0GfJuiFkRSui2fitUo) we always have an error about using map
function on null, but as I understand there shouldn’t be difference in how we create the profile, since we send the same data when creating profile the data in the subscription’s event would be the same. In anyway we can’t see in the logs what event
is passed to the subscription function. We have this https://monosnap.com/file/qn6iu9GPQHz7Q7YR5WF3Ltzt3RjJQo result, the red strings is running createProfile
through the endpoint’s playground or our frontend, the white from the Graphcool Console playground. Please, advice where maybe the problem?Rob Murtagh
02/20/2018, 3:16 PMVentura
02/20/2018, 3:22 PMjacqui
02/20/2018, 3:35 PMjsan
02/20/2018, 3:40 PMjsan
02/20/2018, 3:40 PMERROR
The request could not be satisfied.
CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection.
jsan
02/20/2018, 3:41 PMFitch
02/20/2018, 3:48 PMFitch
02/20/2018, 3:49 PMsenorcodecat
02/20/2018, 6:41 PMsenorcodecat
02/20/2018, 6:42 PMquery {
allUsers (filter: { AND: [
{bootCamps_every: {location: "Anaheim"}},
{bootCampsAttended_none: {location: "Anaheim"}}
]}) {
firstName
lastName
bootCamps {
location
}
bootCampsAttended {
location
}
}
}
picosam
02/20/2018, 7:15 PMListening for transport dt_socket at address: 8000
/opt/jdk1.8.0_162/jre/lib/rt.jar: invalid LOC header (bad signature)
It appears in the local_prisma-database_1
docker container that’s created during the prisma init
process — I then end up having this forever:
local Local cluster (requires Docker)
Booting local development cluster... ⣽
I believe it may be the same issue reported at https://github.com/graphcool/prisma/issues/1901