Pass user-agent from DownloadConfig into fsspec storage_options #7631
+9
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes part of issue #6046
Problem
The
user-agent
defined inDownloadConfig
was not passed down to fsspec-based filesystems likeHfFileSystem
, which prevents proper identification/tracking of client requests.Solution
Added support for injecting the
user-agent
intostorage_options["headers"]
within_prepare_single_hop_path_and_storage_options()
based on theprotocol
.Now, when using
hf://
,http://
, orhttps://
, the custom user-agent is passed automatically.Code Location
Modified:
src/datasets/utils/file_utils.py
Used
get_datasets_user_agent(...)
to ensure proper formatting and fallback logic.