Seems to work again 🙂

Yup!

Hey <!here|@here>! We’re terribly sorry for this long unexpected downtime. We have identified and solved the problem and are fully up and running again. We’ll shortly follow up with a more detailed post-mortem report containing background information how this could have happened and what we’ll do to prevent something like this in the future. Thanks a lot to all of you for your understanding. Let us know if you need any help! 🙏

I have a schema where I have a

User

model, a

Team

model, and there is a 1-to-1 relationship between the two. If I have the

userId

, can I update a

Team

immediately with that

userId

, or do I first have to use the

userId

to query for the

teamId

and then update the user's team with that

teamId

?

Is there an example somewhere of using Apollo Client's optimistic UI when doing a nested mutation?

Whats up Graphcool! Question on your docs. https://www.graph.cool/docs/reference/relay-api/one-node-ga4chied8m

Cheers, brother. Been deep in the code.

lots of awesome folks have joined us recently! 🖖 to you all! @stevewpatterson @richard127 @robert_p @sbornia @jhaubold @msanroman @qard @mkern @edward_s @sstine @komondor @barbatus @davaahoo @anandprabhu @marielle @grst @guilhermescp sorry if I missed anyone, it’s not personal! 🙂 a hearty welcome to you all from the bottom of the graphcool team’s ❤️

Ah, thanks so much @artyom! Really excited at what you all are doing! 🖖

I’m getting a bunch of "Unhandled GraphQL subscription errors” that seem to appear at random times even now when the service seems to be working fine. Any idea how to handle these? Is there a way to catch them?

React Native btw.

We have concluded our investigation of tonights incident. We fixed the immediate issue earlier today and are currently implementing better procedures to make sure this can not happen again. Thank you all for the support! @jshort - I think beers are on us this time. You can read our post mortem at https://status.graph.cool/

One question might be timing these types of changes. I've seen lots of people make changes in the evening/night to minimize downtime but the problem with that is that there can be a long tail to resolution since everyone is asleep. At least first thing on a Tuesday for config changes you know you have 8 hours to work on a problem. Not sure if others have experienced this but I always preferred as a customer to know that an outage was during a time when someone could actually work on it. Obviously this could be different for other folks and I'm not sure what your internal procedures are. Overall thanks for communicating. 🙂

❤️ thanks for the great post mortem. shit happens.

@jimthedev we used to have a flag at an old job on deploy that happened an hour before work ended or on fridays

--yes-i-know-what-time-it-is-and-i-accept-the-consequences

. And then stupid CI/CD came along and I don't get the fun flags in my job anymore.

haha

@jshort I like that. Maybe CI should just always queue changes after a certain time and if you want to push it through then you need to log in to a clowntown site where you have to take a photo of yourself before pushing it through

@jason 🖖 welcome to graphcool !

thanks @artyom

I was looking for info about more advanced authorization schemes but it seems that even permissions based on ownership are in beta?

I would need something more like https://github.com/haruska/pool_madness/blob/master/app/models/ability.rb

Not sure I would need a full custom lambda function for graph.cool but certainly the ability to have more advanced permissions

Hey @jason I'll reach out to in PM 🙂

Hi guys! I have a question. Is the Graphcool Documentation site built using Graphcool?

Is there a way to delete by filter ?

Hi All, Has anybody used anything other than Algolia for full text search? How did you achieve that?

Quick question regarding graphql-up.. Is there a way to tear it down?

@nilan 🎁Stickers received 👍

Hi, everyone! Does anybody have experience using graph.cool with app whose users produce about 2000rpm to the server? What’s response time?

I had 4 users just 30 minutes ago, scaled to 10, holding steady, so I know you can more than double in a short period of time and be great! 😂