forked from fl00r/go-tarantool-1.6
-
Notifications
You must be signed in to change notification settings - Fork 60
golint does not print backtrace #231
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
Labels
Comments
Yes, we need to fix it on CI ( golangci/golangci-lint-action#119 , tarantool/tt#116 ), but on the local machine you could to use the make target:
|
To be honest, it's not really helpful to receive any issues for local run and do not receive them in CI. |
oleg-jukovec
added a commit
that referenced
this issue
Dec 27, 2022
After the patch golangci-lint prints a file and a line number. Closes #231
oleg-jukovec
added a commit
that referenced
this issue
Dec 27, 2022
After the patch golangci-lint prints a file and a line number [1]. 1. golangci/golangci-lint-action#119 Closes #231
oleg-jukovec
added a commit
that referenced
this issue
Dec 27, 2022
After the patch golangci-lint prints a file and a line number [1]. 1. golangci/golangci-lint-action#119 Closes #231
oleg-jukovec
added a commit
that referenced
this issue
Dec 27, 2022
The patch adds a second golangci-lint run that prints errors in human-readable format [1]. 1. golangci/golangci-lint-action#119 Closes #231
oleg-jukovec
added a commit
that referenced
this issue
Dec 28, 2022
The patch adds a second golangci-lint run that prints errors in human-readable format [1]. 1. golangci/golangci-lint-action#119 Closes #231
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
It is a pain to debug errors like
without having any information about what file and line they are referred to.
The text was updated successfully, but these errors were encountered: