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

dirac-dms-find-lfns misbehaves if given an invalid path #7487

Closed
sfayer opened this issue Feb 28, 2024 · 1 comment
Closed

dirac-dms-find-lfns misbehaves if given an invalid path #7487

sfayer opened this issue Feb 28, 2024 · 1 comment
Assignees
Milestone

Comments

@sfayer
Copy link
Member

sfayer commented Feb 28, 2024

Hi,

I've noticed that dirac-dms-find-lfns returns entries even if it's given a Path= filter that points to a directory that doesn't exist. It seems to walk up the tree until it finds a path that does exist and then return all the files under that instead.

$ dirac-version 
8.0.38
$ dirac-dms-find-lfns Path=/gridpp/user/u/user.name/myjob/
/gridpp/user/u/user.name/myjob/job.log
# I'd expect this to say ".../badpath" doesn't exist
$ dirac-dms-find-lfns Path=/gridpp/user/u/user.name/myjob/badpath
/gridpp/user/u/user.name/myjob/job.log
$ dirac-dms-find-lfns Path=/gridpp/user/u/user.name/myjob/badpath/reallybadpath
/gridpp/user/u/user.name/myjob/job.log

(Server catalog backend is normal DIRAC FileCatalog)

I'd expect this to stop with an error rather than return files that don't match the filter! We use this command in a script to handle a specific type of deletion task and as you might imagine, this has resulted in files being removed from the catalogue that shouldn't have been.

Would it be possible for this to be fixed?

Regards,
Simon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants