8000 fix for #359 issue by AverageMarshmallo · Pull Request #360 · tclahr/uac · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix for #359 issue #360

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

Merged
merged 5 commits into from
Apr 25, 2025
Merged

fix for #359 issue #360

merged 5 commits into from 8000
Apr 25, 2025

Conversation

AverageMarshmallo
Copy link

Fixes an issue where setting the max_depth value in the uac.conf configuration file had no effect on the actual search depth used by the tool.

Fixes an issue where setting the max_depth value in the uac.conf configuration file had no effect on the actual search depth used by the tool.
@tclahr
Copy link
Owner
tclahr commented Apr 23, 2025

Actually the fix is even easier. If max_depth is set in uac.conf it should be used by find -maxdepth no matter if max_depth is set or not by artifacts.
So checking if __UAC_CONF_MAX_DEPTH is greater than 0 is enough to change __bf_max_depth value.

I am pushing the new code to your PR.

@tclahr tclahr changed the base branch from main to develop April 23, 2025 21:15
@AverageMarshmallo
Copy link
Author

For some reason I thought that the __UAC_CONF_MAX_DEPTH is needed to specify the search depth for artifacts without explicitly specified search depth.

Thanks anyway.

@tclahr
Copy link
Owner
tclahr commented Apr 24, 2025

My bad. You are right. __UAC_CONF_MAX_DEPTH should force find -maxdepth only on artifacts that have no max_depth set. I will change the code again.

@tclahr tclahr merged commit 687d01e into tclahr:develop Apr 25, 2025
2 checks passed
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.

2 participants
0