Running superlinter as a user not defined in /etc/passwd causes error messages #4351
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #
Proposed Changes
whoami
command to useid -un
and discard stderr. Currently, when running superlinter with a UID that whoami or the id command cannot resolve. Two things happen:A) The following error is emitted:
whoami: cannot find name for user ID 1234
B) In the debug output the contents of "Runner" is blank like this:
[DEBUG] Runner:[]
By changing to
id -un 2>/dev/null
, The error message is not printed, and the Runner is set to the uid if it is unable to determine a username:[DEBUG] Runner:[1234]
The standard behavior is retained when a username can be determined:
[DEBUG] Runner:[root]
Readiness Checklist
Author/Contributor
Reviewing Maintainer
breaking
if this is a large fundamental changeautomation
,bug
,documentation
,enhancement
,infrastructure
, orperformance