-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Following the getting started fails with go1.18beta2 #1961
Comments
Please can you add a github repo for reproduction? Thanks. |
Sure. Additional information: I managed to make it work on a fork by adding |
Here you go: https://github.com/nlepage/gqlgen-issue-1961 |
The error I fixed by adding the There is a go issue about this error: golang/go#45584, not sure if this is related. |
I think we should wait for 1.18 stable to better understand. Please can you monitor this for us? You can close if it works when 1.18 stable is released. Thanks. |
No problem. |
I just tried this using 1.18rc1. It works. |
@adaya-sprobe This issue was reported for gqlgen v0.16.0, it seems to have been fixed in further versions... gqlgen v0.16.0 is still broken with go1.18rc1, and will probably be with the final release. It may have been fixed in gqlgen v0.17.0 by this commit : 9866507#diff-ca34562b44ad709eeae25522801f5282e8a197c52f345d38b13180c1cae88e83 |
The problem reported by this issue is fixed in gqlgen v0.17, so I'm closing this. However I'm still having an issue with generate returning the error: |
The original issue with v0.16 can be solved by upgrading As for the other issue, you can reproduce it using this: https://github.com/Desuuuu/gqlgen-issue Adding the |
I'm still experiencing the |
@ivanvanderbyl @Desuuuu I think this is worth opening another issue. |
Please create a reproduction repo before opening a new issue. |
@frederikhors I think that's what @Desuuuu did, as mentionned in #1961 (comment) : https://github.com/Desuuuu/gqlgen-issue |
The It has been reported here. |
I think we should wait for 1.18 official to re-open this. |
@frederikhors go1.18 is out and as far as I can tell this is still an issue with gqlgen 17.1 it can be fixed by adding NeedDeps |
@StevenACoffman I think we have a problem with Go 1.18. I'm reopening this. :( |
Signed-off-by: Steve Coffman <steve@khanacademy.org>
Thanks very much @nlepage, @mojtabacazi, @Desuuuu , and @ivanvanderbyl and @frederikhors ! |
BTW, I cut a new gqlgen v0.17.2 release now that Go 1.18 is out and I didn't see any reports of issues with the fix. |
Go 1.18 is out! So we should run tests on it. gqlgen had some issues with it (see 99designs/gqlgen#1961 and golang/go#45584) so I updated that too, which updated some other things. Test plan: make check
Go 1.18 is out! So we should run tests on it. Additionally, gqlgen had some issues with it (see 99designs/gqlgen#1961 and golang/go#45584) so I updated that too, which updated some other things. Finally, latest gqlgen requires 1.16+, and it's time for us to do the same anyway, so we can use `embed` and other newer goodies. So I dropped running tests for 1.14 and 1.15, and bumped the module language version. Test plan: make check
Go 1.18 is out! So we should run tests on it. Additionally, gqlgen had some issues with it (see 99designs/gqlgen#1961 and golang/go#45584) so I updated that too, which updated some other things. Finally, latest gqlgen requires 1.16+, and it's time for us to do the same anyway, so we can use `embed` and other newer goodies. So I dropped running tests for 1.14 and 1.15, and bumped the module language version. Test plan: make check
Hello I'm running the tutorial and running gqlgen v0.17.2 and go1.18 windows/amd64 it appears that the command 'go run github.com/99designs/gqlgen init' causes this same issue again |
What happened?
Trying to follow the getting started fails at step
go run github.com/99designs/gqlgen init
.Adding the
--verbose
flag produces the following error message:Further executions of the
generate
command produce the same error.What did you expect?
Being able to go through the getting started without errors.
Minimal graphql.schema and models to reproduce
N/A
versions
gqlgen v0.16.0
go v1.18beta2
Complete logs (reproduced in a docker container)
The text was updated successfully, but these errors were encountered: