-
Notifications
You must be signed in to change notification settings - Fork 18.8k
go-swagger: fix panic under Golang 1.13 #40038
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll have to add a commit that changes the swagger.yaml, otherwise go-swagger won't run
Failing, looks like you're referencing a wrong commit;
|
It's just I added a comment to an inappropriate place. Removed. |
ah, lol you just pushed again |
OK looks like it works:
Now I'm not sure what would be the best way to have it. Temporary, we can merge this one as-is (removing the second commit of course). Longer-term, IDK. |
Some thoughts;
|
Dockerfile
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we decide to merge this; perhaps we should tag the commit (also wondering if the fork should live in the moby
org, so that it's not tied to a personal account)
OK here's my plan
|
Dockerfile
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a TODO comment, and open a tracking issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
This is an attempt to fix go-swagger panic under Golang 1.13. Details: * go-openapi/jsonpointer#4 * go-swagger/go-swagger#2059 Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Rebased, added TODO |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Weird; CI Hung after tests completed; https://ci.docker.com/public/job/moby/job/PR-40038/6/execution/node/195/log/?consoleFull
|
This is an attempt to fix go-swagger panic under Golang 1.13.
Detai 8000 ls:
Failure: