go-swagger: fix panic under Golang 1.13#40038
Conversation
thaJeztah
left a comment
There was a problem hiding this comment.
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.
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.
Can you add a TODO comment, and open a tracking issue?
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 <[email protected]>
|
Rebased, added TODO |
|
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.
Details:
Failure: