It seems not working for nested connect with creat...
# prisma-whats-newm
Michael
03/18/2018, 11:32 AMIt seems not working for nested connect with create at the same time? any suggestion?
d
Daniel K.
03/18/2018, 11:46 AMand what's in the logs ? 🙂
m
Michael
03/18/2018, 11:52 AMin terminal or cluster? not sure how to find cluster log in docker
d
Daniel K.
03/18/2018, 11:53 AMyou should have logs by default in terminal where is your server running
m
Michael
03/18/2018, 11:53 AM Copy code
[GraphQL error]: Message: Whoops. Looks like an internal server error. Search your cluster logs for request ID: api:api:cjewqmlmy00hm0902m3l2rvfj, Location: [object Object], Path: createOrder
[Network error]: Error: Whoops. Looks like an internal server error. Search your cluster logs for request ID: api:api:cjewqmlmy00hm0902m3l2rvfj
Error: Whoops. Looks like an internal server error. Search your cluster logs for request ID: api:api:cjewqmlmy00hm0902m3l2rvfj
at BatchedGraphQLClient.<anonymous> (/Users/wanghk/code/Meerkat/local_server/node_modules/http-link-dataloader/src/BatchedGraphQLClient.ts:68:15)
at step (/Users/wanghk/code/Meerkat/local_server/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:40:23)
at Object.next (/Users/wanghk/code/Meerkat/local_server/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:21:53)
at fulfilled (/Users/wanghk/code/Meerkat/local_server/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:12:58)
at <anonymous>
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
^Cd
Daniel K.
03/18/2018, 11:55 AMwell ... 🙂 so that's an issue in database layer itself apparently, I guess you can try
docker logs <container>m
Michael
03/18/2018, 12:05 PMit’s long log hope wont trouble you
Michael
03/18/2018, 12:08 PMtrying to use prisma in cloud and local, but with same error, so im afraid if it caused by creating nodes with connecting at same time