There is maybe a “bug” 🐛 on the local deployments, it looks like when we add a new model we need to restart the container. I don’t know if this is the expected behaviour or if it’s a bug, can someone confirm that, maybe it’s just for me

What is the exact behaviour you’re experiencing? What is the expected behaviour?

I added a new model on my types.graphql, with some enums and relations and after the deployment the diff was ok (with the modifications) but I couldn’t access this model (even with the

__schema { types { name } }

query). I needed to restart my container to have it. I would expect like when I deploy to graphcool to have it just after the deployment is done the model is here and accessible without restarting the container But I don’t know this may be me doing something wrong, at first I had a model with numbers in the name I was thinking this was the problem so I renamed everything but still didn’t have my model

There were schema invalidation issues two days back, can you try to pull the newest images with

graphcool local pull

and then

graphcool local up

and see if the issue persists?

yes i did the pull after that, I didn’t re-update my models so didn’t reproduce yet, I will have to migrate my models probably during the day, i will test again

Cool, thanks.

just added one fields on my models and it works without restart, I don’t know if it’s because of the pull or maybe before i had some errors or something like that but looks like I cannot reproduce

Awesome, thanks for sharing.