Skip to content

fix: fix glob expression illegal operations on directories - #1308

Merged
Ffloriel merged 2 commits into
FullHuman:mainfrom
aminya:glob-issues
Feb 2, 2025
Merged

Ffloriel merged 2 commits into
FullHuman:mainfrom
aminya:glob-issues

Conversation

@aminya

@aminya aminya commented Dec 15, 2024

Copy link
Copy Markdown
Contributor

This fixes the glob regression issues from v5 + parallelizes the async IO operations for faster purge.

Proposed changes

Fixes an issue that the previously working glob expressions no longer work in v6 and v7. This changes the glob dependency to fast-glob to fix the issue.
Fixes #1266

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

This fixes the glob regression issues from v5 + parallelizes the async IO operations for faster purge.

## Proposed changes

Fixes an issue that the previously working glob expressions no longer work in v6 and v7. This changes the glob dependency to fast-glob to fix the issue. I also parallelized the async-io operations for faster purge.
Fixes FullHuman#1266

## Types of changes

What types of changes does your code introduce?
_Put an `x` in the boxes that apply_

- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

## Checklist

_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._

- [x] Lint and unit tests pass locally with my changes
- [x] I have added tests that prove my fix is effective or that my feature works
- [ ] I have added necessary documentation (if appropriate)

## Further comments
@Ffloriel
Ffloriel merged commit b27293f into FullHuman:main Feb 2, 2025
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.

[Bug]: Upgrading from 5 to 6: illegal operation on a directory

2 participants