What happens if I create a 1-to-1 relationship, but later make it 1-to-many?

Experiencing internal servers errors w/graphql-up using just the basic User-Tweet example

basically I am on the cli and get ✖️ There was an error: Internal server error

More info on the graphql-up error:

content-length →36
content-type →application/json
date →Thu, 23 Mar 2017 05:40:51 GMT
status →502
via →1.1 <http://38aa508962be3eec6873d3e4e464e6b4.cloudfront.net|38aa508962be3eec6873d3e4e464e6b4.cloudfront.net> (CloudFront)
x-amz-cf-id →sbkslsKR3DqZKk7F6N4DK_p54rjjbWkIhO_1wmvL6aIiuIoqOgzRvg==
x-amzn-requestid →46586c38-0f8b-11e7-a0cd-27e2c94c630c
x-cache →Error from cloudfront

@jimthedev Thanks a lot for the error report.

graphql-up

is 🆙 again!

Is there somebody who have issue with relations ? because it's not working in my side, i got error

i cannot create or delete

@schickling here!

Welcome @jshort 👋 🙂 Glad you find your way into our Slack

Hello from Denver

Hello back from Berlin @jeffdiers 🌎

One time I was in a job interview and they asked me to architect a system and I just responded “graph.cool” and walked out.

That is not entirely true, but ooph I love the service so much.

@nickhudkins that had us laughing so much 😄

apparently! haha well I am glad I could bring a smile to your faces!

you should definitely make that a tweet @graphcool it will go through the roof! 🚀

did it!

planned downtime? Getting `502`s

same

is graph.cool down?

Hmm, has CORS been enabled overnight or something? Getting `502`s as well.

is it the console or also the API?

even my apps are down

@nilan, looks like the console may be as well

Same here

a bunch of client side errors there

I was able to get back in by forcing a logout

right