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

The 'check-manifest' pre-commit hook is very slow #169

Closed
csadorf opened this issue Apr 12, 2021 · 4 comments
Closed

The 'check-manifest' pre-commit hook is very slow #169

csadorf opened this issue Apr 12, 2021 · 4 comments

Comments

@csadorf
Copy link
Member

csadorf commented Apr 12, 2021

Running this pre-commit hook sometimes takes more than two minutes (see log below) – significantly slowing down my development workflow – and its benefit is not entirely clear to me. @chrisjsewell Since you originally introduced this hook, could you briefly comment what we use it for in this project and whether we could maybe limit it to run when only certain files are changed, such as setup.cfg?

% pre-commit run -v check-manifest
check-manifest...........................................................Passed
- hook id: check-manifest
- duration: 129.4s

lists of files in version control and sdist match
@csadorf csadorf added the bug Something isn't working label Apr 12, 2021
@chrisjsewell
Copy link
Contributor

@csadorf
Copy link
Member Author

csadorf commented Apr 13, 2021

As a temporary remedy, I've set the $SKIP environment variable in my dev environment: export SKIP=check-manifest

@csadorf csadorf removed the bug Something isn't working label Apr 13, 2021
@chrisjsewell
Copy link
Contributor

@csadorf, I would just try adding as it suggests:

  - repo: https://github.com/mgedmin/check-manifest
    rev: "0.46"
    hooks:
    - id: check-manifest
      args: [--no-build-isolation]
      additional_dependencies: [setuptools>=46.4.0]

@csadorf
Copy link
Member Author

csadorf commented May 12, 2021

The pre-commit check now runs reasonably fast in my development environments. This appears to have been resolved upstream.

@csadorf csadorf closed this as completed May 12, 2021
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

No branches or pull requests

2 participants