-
Notifications
You must be signed in to change notification settings - Fork 273
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
new VCS repo scanning: file exclusion not working properly #4783
Comments
I have migrated our stack from using |
Good catch @hnicke – thanks for the detailed report! 👍 |
@hnicke If you could provide a minimal example in the mean time to reproduce, that would be perfect (e.g. a simple one-file garden yaml with an exclude that counts 2 files instead of one – do excludes work with some module / action kinds, but not others?) |
I currently don't have the time to provide a full example, but here's the gist: Given the The project config is configured to ignore node_modules:
The following module (without further ignorefiles) will take ages to scan (i.e., # example.garden.yml
kind: Module
type: container
name: example
exclude:
- node_modules/** The logs ( However, when changing the module like this, the perfomance issue is gone: # example.garden.yml
kind: Module
type: container
name: example # .gardenignore
node_modules By the way - in my case the module is located in a remote source - not sure if that is a factor that has to be taken into account. |
Thank you for the more detailed information We were able to reproduce successfully Steps to reproduce
Observed behaviourWith
Expected behaviourI would expect the same number of files as without
|
@hnicke is this still an issue in |
I tried the repro from @stefreak in
I assume we can consider this fixed then? |
Bug
Current Behavior
I have tried the new VCS repo scanning algorithm (
scan.git.mode: repo
) that ships with v0.13.7 (#4642) since I hoped it would help with the stack resolution performance problems described in #4763.Something is off with the file exclusion.
E.g., one module with ~1100 files (without new algorithm) now has around ~10000, according to the log.
Another module (with node_modules folder) normally has ~1000 files (without new algorithm), with new algorithm log reports there are ~200000 files.
I have defined all exclusions via module config
excludes
array.It seems they don't work properly.
Therefore, with the new vcs algorithm
garden validate
takes >5 minutes.Expected behavior
Both repo scanning algorithms detect the same amount of files for each module.
Workaround
Use
.gardenignore
files for file exclusions instead ofexclude
in module /action configuration.Your environment
garden version
0.13.7
@edvald might be interesting for you
The text was updated successfully, but these errors were encountered: