I'm not entirely sure how to debug this one, but it seems to be crashing in this call in ./internal/packages.go
defaultPackage, err := config.Packages.Load(defaultModelPath)
I noticed that if the lambda directory is deleted, and then init and generate are called, it is possible to successfully generate as long as schema.graphql is incredibly simple.
I made a "sanity check" instance at the following URL which can bootstrap a dgraph and lambda instance in the docker-compose.yaml
https://github.com/nargetdev/go-lambda-sanity-check
I'd love to hear your thoughts @Schartey --- am I barking up the wrong tree here? Should I ditch main entirely and just focus on next? Do you have any documentation for next? Is the interface the same (i.e. run init and then generate)? I haven't had success with next yet, but I also have never used WASM..
Cheers mate,
thanks for creating this project.
I'm not entirely sure how to debug this one, but it seems to be crashing in this call in
./internal/packages.goI noticed that if the
lambdadirectory is deleted, and theninitandgenerateare called, it is possible to successfully generate as long asschema.graphqlis incredibly simple.I made a "sanity check" instance at the following URL which can bootstrap a dgraph and lambda instance in the
docker-compose.yamlhttps://github.com/nargetdev/go-lambda-sanity-check
I'd love to hear your thoughts @Schartey --- am I barking up the wrong tree here? Should I ditch
mainentirely and just focus onnext? Do you have any documentation fornext? Is the interface the same (i.e. runinitand thengenerate)? I haven't had success withnextyet, but I also have never used WASM..Cheers mate,
thanks for creating this project.