-
Notifications
You must be signed in to change notification settings - Fork 76
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
uproot
cannot write root files over xrootd.
#1252
Comments
@jpivarski when you find some time, please look into this as well. |
The exception seems to be coming from xrootd, not fsspec. I can't say why the file didn't truncate. |
@amadio gave us an alternative in xrootd/xrootd#2304 (comment), which can replace uproot5/src/uproot/sink/file.py Lines 70 to 81 in aa8b94f
(which calls truncate in fsspec-xrootd). It is only ever called from uproot5/src/uproot/sink/file.py Lines 52 to 53 in aa8b94f
@amadio's alternative involves opening the file with a different set of flags. @maxgalli, do you think that can be implemented in Uproot, or does that fix need to go into fsspec-xrootd? I was at first thinking that we could do it, but after looking at the code references, it doesn't look like we have direct access to the |
Hi @jpivarski, sorry for the late reply. It seems to me that implementing Guillerme's suggestion into fsspec-xrootd might be the way to go, but I'm not sure as I'm not familiar with the code yet. I will look into this in more detail in a few weeks from now, after thesis submission (I would thus keep the issue open for now if it is ok). |
dask_write
cannot write over xrootd.uproot
cannot write root files over xrootd.
I'm confused, why do we need to have |
Since you later want to open a file with truncate on open, I would suggest to use that interface in fsspec-xrootd. Open the file with mode |
Furthermore, I suspect interacting in read-write mode with a remote filesystem is not a great idea. We should encourage users to add the |
Hi Nick, I came back to this, doing some investigation and trying to follow your suggestion. However, there are a few things I don't understand. |
Ah, this might be a mistake, perhaps we can allow Did you try the |
I think the comment might refer to this: the inherited
Not yet, I'm still trying to find a combination of changes in uproot/fsspec/fsspec-xrootd that fixes the bug - will add it here. |
To reproduce:
fails with:
The below reproducers work fine locally but will fail if
"dummy"
becomes a remote xrootd path.The text was updated successfully, but these errors were encountered: