-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Unable to use EOS tokens with RDataFrame since 6.32 #16475
Comments
Dear @chrisburr , Thank you for reaching out and for the reproducer. I am on it. Meanwhile, I just wanted to point out that for the first case in 6.30, just calling |
Thanks! This definitely used to be working (with 6.28 IIRC). If I find a minute I'll check with 6.30. |
The problem is that RDF tries to open the file to check that it's valid. The logic for the file opening is at root/tree/dataframe/src/RLoopManager.cxx Line 1133 in 962009b
? token, the string is parsed as a glob. Now in many cases that would be harmless albeit a tiny overhead (it would just return the same file name to open), but in this particular case it triggers a faulty behaviour. The glob parsing attempts at traversing the remote xrootd directory (see here), but since the permission is just for the single file with the token and not for the entire directory, it leads to the user access restricted error you post above.
Now, I believe the most sane course of action would be to refine the logic that checks whether the input file name is a glob. I could simply add a check for the |
Ah that makes sense. Extending the defintion of strings to add metadata to paths (globbing, the
This feels like an impossible task to define. Maybe a simplier solution would be to not support |
Check duplicate issues.
Description
EOS tokens no longer work with RDataFrame in 6.32.04. In 6.30.08 everything is fine:
Reproducer
On lxplus:
ROOT version
6.32.04
Installation method
sft.cern.ch
Operating system
Linux (lxplus)
Additional context
No response
The text was updated successfully, but these errors were encountered: