-
Notifications
You must be signed in to change notification settings - Fork 44
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
Fatal on scanning a dir #182
Comments
Just checked, v0.3.0 works fine on same dir. |
Reinstalling v0.4.0 fixed this. Weird. Feel free to close this if not able to reproduce |
Ok the issue crops up when using docker image for v0.4.0
|
I think this might have been introduced on a bump of license classifier from this PR #167 I just built a local copy of |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
This was fixed in #161 /close |
@puerco: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'm using v0.4.0.
Following is error I'm getting.
The text was updated successfully, but these errors were encountered: