Skip to content

Conversation

@thaJeztah
Copy link
Owner

@thaJeztah thaJeztah commented Jan 28, 2022

glog has the same issue as k8s.io/klog, and is calling user.Current()
inside an init(); see kubernetes/klog@466fbb6

Calling user.Current() on Windows can result in remove connections being
made to get the user's information, which can be a heavy call. See docker/cli#2420 and docker/cli#2515

glog was only used in a single location, so we may as well remove it.

thaJeztah and others added 2 commits January 28, 2022 15:26
We're using dependencies with this license in many places, and it should
be ok to use.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
…cense_check

license-check: add BSD-3-Clause to allow-list
thaJeztah and others added 5 commits January 28, 2022 16:28
Older versions may have issues when running recent Alpine images,
due to seccomp profiles not being up to date with latest kernels.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
Signed-off-by: Sebastiaan van Stijn <[email protected]>
Hoping to fix:

    Output from proc 3:
      flag provided but not defined: -ginkgo.timeout
      Usage of /e2e.test:
        -alsologtostderr
          	log to standard error as well as files
        -ginkgo.dryRun
          	If set, ginkgo will walk the test hierarchy without actually running anything.  Best paired with -v.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
glog has the same issue as k8s.io/klog, and is calling `user.Current()`
inside an `init()`; see kubernetes/klog@466fbb6

Calling `user.Current()` on Windows can result in remove connections being
made to get the user's information, which can be a heavy call.

glog was only used in a single location, so we may as well remove it.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants