im sure someone is getting aphone call and waking up right now… 10,000 people in this slack.. plus all the devs who aren’t here… we aren’t the only ones who noticing haha

@tsdexter Thankd for the info. I was hoping to avoid that complexity. I don't need graph.ql but it is a great technology. If I have to do all of that, I may change the backend.

^bump

i got first customer report of the 504 error 1 hour 13 minutes ago. Hopefully someone notices soon

for a simple app, it’s probably not much.. especially free hosting on heroku or something… but it sure can get more complicated.. especially if you started on graphcool and are migrating.. if I started with prisma i’d be a lot less apprehensive about it

@tsdexter yeah that sounds like a serious migration, not fun.

@justSlone I am seeing an Error: Could not fetch schema from https://api.graph.cool/simple/v1/xxxxx/permissions. from the playground., Seems to be an internal error t

yeah that's the same error, it seems to be a 504 under the covers

an internal error so yes but this seems to be pretty low level

i see both could not fetch schema and type error: failed to fetch

any automated system shouldn't just ping

im getting a

Error: Network request failed with status 504 - "Gateway Time-out"

which is a response via a cloudfront HTML error page, which is then causing:

FetchError: invalid json response body at <https://api.graph.cool/simple/v1/xxxx> reason: Unexpected token < in JSON at position 0

because the response starts with

<DOCTYPE html>

@tsdexter yep, same thing Cloudfront text is ... <H1>504 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection. <BR clear="all"/> For more information on how to troubleshoot this error, please refer to the CloudFront documentation ( <A href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-504-gateway-timeout.html">https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-504-gateway-timeout.html</A>). <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: 04Dbpj1434T4BGMvUmHxC2NQN2fR2VChiQHkC0X9fJ2WUPS6TwFCSQ== ...

guess ill just go to sleep and hope when my users get to work in 6 hours it works… 😞

good news is that your site should just work when it comes back up 🙂

one good thing from this… a reminder that I need a prettier error message from my server side rendering….

customer wont like that haha

yeah... I just deployed a fix to my error message code 🙂

haha smart..

it was just rendering a blank page whoops

maybe i should before bed

🙄

I would, "Check your source code" is a pretty evil error message when it's not their fault 🙂

haha, yeah deploying now

one thing i dislike about app engine is that it takes 10-15 mins to deploy even the smallest change

@tsdexter boo 😞

yeah I have a small site, just using s3 websites. build is 45 seconds client side, deploy is 30 second filecopy 🙂

amazing

haha