-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Bump Golang 1.12.3 #1818
Bump Golang 1.12.3 #1818
Conversation
Signed-off-by: Jintao Zhang <zhangjintao9020@gmail.com>
- ps: .\scripts\make.ps1 -TestUnit |
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.
This change is because of no newline at end of file.
@@ -1,4 +1,4 @@ | |||
FROM dockercore/golang-cross:1.12.2@sha256:ea93d7ed5b464e5163cf8df40a198ad54afe6a59e1ca335c9bc4a5ed3702f2d0 | |||
FROM dockercore/golang-cross:1.12.3@sha256:b88a6be2469d321601f87675c49d1b3f166c4c37abc5ce3e74557fc6660481be |
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.
as @thaJeztah said,
I'm actually thinking of removing this "pin by digest", as it doesn't add much for our use-case 🤔
I also agree very much. Do we need to remove this "pin by digest" ? 🤔
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.
I am ok with removing it
@vdemeester @silvin-lubecki SGTY?
It seems that the lint task failed, I ran the lint task locally and found that it takes 4m+.
should we increasing deadline? 🤔 |
Codecov Report
@@ Coverage Diff @@
## master #1818 +/- ##
=======================================
Coverage 56.31% 56.31%
=======================================
Files 308 308
Lines 21429 21429
=======================================
Hits 12068 12068
Misses 8476 8476
Partials 885 885 |
And I found gometalinter has been archived by the owner. alecthomas/gometalinter#590 should we change to use golangci-lint or other active lint tool? |
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.
Thanks!
Left one question about the timeout, and let's wait for the others to reply wrt the digest
@@ -1,4 +1,4 @@ | |||
FROM dockercore/golang-cross:1.12.2@sha256:ea93d7ed5b464e5163cf8df40a198ad54afe6a59e1ca335c9bc4a5ed3702f2d0 | |||
FROM dockercore/golang-cross:1.12.3@sha256:b88a6be2469d321601f87675c49d1b3f166c4c37abc5ce3e74557fc6660481be |
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.
I am ok with removing it
@vdemeester @silvin-lubecki SGTY?
6456505
to
c55c801
Compare
For the linter: I just recalled there's a pull request to replace it (that I didn't review yet 🤭🤫😳) #1797 |
Interesting;
|
( nolint directive did not match any issue (nolint)) |
Sorry, I didn't notice its existence. I just tried to change gometalinter to golangci-lint locally. 😆 |
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, all green now 👍
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 🐯
Signed-off-by: Jintao Zhang zhangjintao9020@gmail.com
- What I did
go1.12.3 (released 2019/04/08) fixes an issue where using the prebuilt binary releases on older versions of GNU/Linux led to failures when linking programs that used cgo. golang/go#31293
see: https://github.com/golang/go/issues?utf8=✓&q=milestone%3AGo1.12.3