Skip to content
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

[Bug]: liccheck not picking license name #2021

Closed
lathashree01 opened this issue Apr 24, 2024 · 2 comments · Fixed by #2074
Closed

[Bug]: liccheck not picking license name #2021

lathashree01 opened this issue Apr 24, 2024 · 2 comments · Fixed by #2074

Comments

@lathashree01
Copy link

Describe the bug

when I run liccheck, the output is empty.

I see the license is Apache 2.0, but it would be great it that metadata could be picked by liccheck.

1 package.
    anomalib (1.0.1): ['']
      dependency:
          anomalib

Dataset

N/A

Model

N/A

Steps to reproduce the behavior

run liccheck with Anomalib in requirements.txt

OS information

OS information:

  • OS: [e.g. Ubuntu 20.04]
  • Python version: [e.g. 3.10.0]
  • Anomalib version: [e.g. 0.3.6]
  • PyTorch version: [e.g. 1.9.0]
  • CUDA/cuDNN version: [e.g. 11.1]
  • GPU models and configuration: [e.g. 2x GeForce RTX 3090]
  • Any other relevant information: [e.g. I'm using a custom dataset]

Expected behavior

Fetch - Apache-2.0 license as license

Screenshots

No response

Pip/GitHub

pip

What version/branch did you use?

1.1.0

Configuration YAML

NA

Logs

1 package.
    anomalib (1.0.1): ['']
      dependency:
          anomalib


### Code of Conduct

- [X] I agree to follow this project's Code of Conduct
@lathashree01 lathashree01 changed the title [Bug]: liccheck not p[icking license name [Bug]: liccheck not picking license name Apr 24, 2024
@samet-akcay
Copy link
Contributor

@lathashree01, PR #2074 should hopefully fix it

@lathashree01
Copy link
Author

Thanks for adding this.

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 a pull request may close this issue.

2 participants