Hi everyone, since I've cleaned my docker volumes with docker rm volume, my code doesn't work anymore. Doesn't feel normal, anyone else experienced this issue ?

did you try

prisma deploy

?

In fact I did prisma generate, but I've just done prisma deploy and still have the same error

What error?

interface conversion: interface {} is nil, not map[string]interface {} goroutine 18 [running]: runtime/debug.Stack(0x1, 0x0, 0x0) /snap/go/2117/src/runtime/debug/stack.go:24 +0xa7 runtime/debug.PrintStack() /snap/go/2117/src/runtime/debug/stack.go:16 +0x22 github.com/99designs/gqlgen/graphql.DefaultRecover(0xa63940, 0xc4202dcfc0, 0x7f99e0, 0xc4202a3000, 0xc420350c70, 0x7c11c0) /home/sacha/go/src/github.com/99designs/gqlgen/graphql/recovery.go:16 +0xbe main.(*executionContext).FieldMiddleware.func1(0xc4202e4430, 0xa63940, 0xc4202dcfc0, 0xc420351818) /home/sacha/go/src/prisma-examples/go-graphql/server/generated.go:2461 +0x76 panic(0x7f99e0, 0xc4202a3000) /snap/go/2117/src/runtime/panic.go:491 +0x283 prisma-examples/go-graphql/prisma-client.PostExec.Exec(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc4202f6150, 0x1, 0x1, 0x0, ...) /home/sacha/go/src/prisma-examples/go-graphql/prisma-client/prisma.go:2886 +0x15e1 main.(*mutationResolver).CreateDraft(0xc420342070, 0xa63940, 0xc4202dcfc0, 0xc42033e02d, 0xa, 0xc42033e044, 0x7, 0xc42033e05c, 0xa, 0x0, ...) /home/sacha/go/src/prisma-examples/go-graphql/server/resolver.go:37 +0x5b0 main.(*executionContext)._Mutation_createDraft.func1(0xa63940, 0xc4202dcfc0, 0x783266, 0xc42013b7a0, 0xc42013b7a8, 0xc42013b7d8) /home/sacha/go/src/prisma-examples/go-graphql/server/generated.go:464 +0x230 github.com/99designs/gqlgen/graphql.DefaultResolverMiddleware(0xa63940, 0xc4202dcfc0, 0xc4202e07a0, 0xa63940, 0xc4202dcfc0, 0xc42013b818, 0xc4202e07a0) /home/sacha/go/src/github.com/99designs/gqlgen/graphql/context.go:33 +0x3a main.(*executionContext).FieldMiddleware(0xc4202e4430, 0xa63940, 0xc4202dcfc0, 0x0, 0x0, 0xc4202e07a0, 0x0, 0x0) /home/sacha/go/src/prisma-examples/go-graphql/server/generated.go:2465 +0xac main.(*executionContext)._Mutation_createDraft(0xc4202e4430, 0xa63940, 0xc4202dcfc0, 0xc4202e2380, 0xc4202dced0, 0x3, 0x3, 0x1, 0xc4202e0780) /home/sacha/go/src/prisma-examples/go-graphql/server/generated.go:463 +0x1e7 main.(*executionContext)._Mutation(0xc4202e4430, 0xa63940, 0xc4202dcf00, 0xc4202e41b0, 0x1, 0x1, 0x7fb9e3bcc1e8, 0x0) /home/sacha/go/src/prisma-examples/go-graphql/server/generated.go:430 +0x564 main.(*executableSchema).Mutation.func1(0xa63940, 0xc4202dce70, 0x819820, 0x800901, 0xc4202e0760) /home/sacha/go/src/prisma-examples/go-graphql/server/generated.go:390 +0x61 github.com/99designs/gqlgen/graphql.DefaultRequestMiddleware(0xa63940, 0xc4202dce70, 0xc4202e0760, 0x8b88d0, 0xc42013bb48, 0xc42013bb48) /home/sacha/go/src/github.com/99designs/gqlgen/graphql/context.go:41 +0x3a main.(*executableSchema).Mutation(0xc420170000, 0xa63940, 0xc4202dce70, 0xc4202f6070, 0xc4202dce70) /home/sacha/go/src/prisma-examples/go-graphql/server/generated.go:389 +0xfa github.com/99designs/gqlgen/handler.GraphQL.func1(0xa63240, 0xc420336000, 0xc42032e000) /home/sacha/go/src/github.com/99designs/gqlgen/handler/graphql.go:255 +0x700 net/http.HandlerFunc.ServeHTTP(0xc4201271a0, 0xa63240, 0xc420336000, 0xc42032e000) /snap/go/2117/src/net/http/server.go:1918 +0x44 net/http.(*ServeMux).ServeHTTP(0xa9d3e0, 0xa63240, 0xc420336000, 0xc42032e000) /snap/go/2117/src/net/http/server.go:2254 +0x130 net/http.serverHandler.ServeHTTP(0xc420130680, 0xa63240, 0xc420336000, 0xc42032e000) /snap/go/2117/src/net/http/server.go:2619 +0xb4 net/http.(*conn).serve(0xc4201700a0, 0xa63880, 0xc420152500) /snap/go/2117/src/net/http/server.go:1801 +0x71d created by net/http.(*Server).Serve /snap/go/2117/src/net/http/server.go:2720 +0x288 ^Csignal: interrupt

This issue is documented here: https://github.com/prisma/prisma/issues/3190

But the code did work just before I have the bad idea to clean the volumes (which doesn't seem to be a good practice)

I cannot think of a reason why that might be related.

might be related to my cli, and the docker image not in sync on the same version I'll see

I think a comment in the issue I shared is helpful 🙂

Okay I commented the issue here https://github.com/prisma/prisma/issues/3190#issuecomment-427869755 . Thank's for the great support 👍