-
Notifications
You must be signed in to change notification settings - Fork 597
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
[CI] golang linter configuration + bootstrapper fixes #1743
Conversation
7f19847
to
be5aef0
Compare
ErrFailUpdate = errors.New("failed to update") | ||
ErrFailCreate = errors.New("failed to create") | ||
ErrCgroupNotExist = errors.New("cgroup does not exist") |
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 would rather keep error message starting with caps, easier to spot when embedded in other messages
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.
on the contrary. Golang usually goes with chaining in logging akin to err3: err2: err1
and actively encourages lowercase. On top of it if you include error messages within logs it may make sentences weird with sudden capitalization.
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.
Good to go after comments addressed
246163c
to
b655305
Compare
b655305
to
f7b16b1
Compare
Fixes CI/build messed up by #1743
Fixes CI/build messed up by #1743
No description provided.