Skip to content

fix: add tos scheme to registry #1878

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 2 commits into from
Jul 1, 2025
Merged

Conversation

yanghua
Copy link
Contributor

@yanghua yanghua commented Jun 25, 2025

The tosfs is a wrong scheme. The right scheme is tos

@martindurant
Copy link
Member

Do you think anyone might already be using "tosfs" as a protocol, should we keep both? I do see that "tos" is indeed the protocol at https://github.com/fsspec/tosfs/blob/main/tosfs/core.py#L104

@yanghua
Copy link
Contributor Author

yanghua commented Jun 26, 2025

Sounds reasonable.

@yanghua yanghua force-pushed the fix-register-tos branch from c74e631 to a04adfa Compare June 26, 2025 02:10
@yanghua yanghua changed the title fix: wrong scheme via replacing tosfs to tos fix: add tos scheme to registry Jun 26, 2025
@yanghua
Copy link
Contributor Author

yanghua commented Jun 27, 2025

@martindurant, please take a look. Thank you.

@martindurant martindurant merged commit 76bd006 into fsspec:master Jul 1, 2025
10 checks passed
@yanghua yanghua deleted the fix-register-tos branch July 2, 2025 00:47
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