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

Fix read_bytes #52

Merged
merged 1 commit into from
Mar 5, 2024
Merged

Fix read_bytes #52

merged 1 commit into from
Mar 5, 2024

Conversation

chrisburr
Copy link
Member

No description provided.

Copy link
Member

@nsmith- nsmith- left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This adds the option of not specifying start and end to _cat_file. Is this a feature of other fsspec filesystems that we didn't support previously? In any case, it's a good addition.

@chrisburr
Copy link
Member Author

Yes. After running into this bug, I wrote test_read_bytes_fsspec against a local file to make sure I understood the expected behavior and then fixed fsspec-xrootd.

@nsmith- nsmith- merged commit 72c5b28 into scikit-hep:main Mar 5, 2024
7 checks passed
@chrisburr chrisburr deleted the read_bytes branch March 5, 2024 16:41
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