fix: pass --s3-no-head-object to rclone for dataset uploads#146
Merged
Conversation
rclone v1.72 changed how its S3 backend handles a 403 from the FS-init HeadObject probe (rclone/rclone#8975, commit rclone/rclone@6440052f, 2025-11-18): non-NotFound errors now propagate as fatal NewFs failures instead of being silently treated as "this is a directory". For BlobTree dataset uploads the platform's session credentials are scoped to <prefix>/<version>/* and HEAD on the bare <version> key is denied — so once Rclone_jll resolved to >= v1.72 (currently v1.73.5), every BlobTree upload aborted with `JuliaHubError: Data upload failed`. The destination is always a directory in our usage, so the probe serves no purpose; suppress it with --s3-no-head-object. Verified locally against internal.juliahub.com with Rclone_jll v1.73.5: the live datasets testset now passes end-to-end, where it previously failed at datasets-live.jl:70 (BlobTree upload). The flag has existed in rclone since v1.55 (2021), so no compat impact.
hariprasad326
approved these changes
Apr 30, 2026
pfitzseb
approved these changes
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
rclone v1.72 changed how its S3 backend handles a 403 from the FS-init HeadObject probe (rclone/rclone#8975, commit rclone/rclone@6440052f, 2025-11-18): non-NotFound errors now propagate as fatal
NewFsfailures instead of being silently treated as "this is a directory".For BlobTree dataset uploads the platform's session credentials are scoped to
<prefix>/<version>/*and HEAD on the bare<version>key is denied — so onceRclone_jllresolved to ≥ v1.72 (currently v1.73.5), every BlobTree upload aborted withJuliaHubError: Data upload failed.The destination is always a directory in our usage, so the probe serves no purpose; suppress it with
--s3-no-head-object.Verified locally against
internal.juliahub.comwithRclone_jllv1.73.5: the live datasets testset now passes end-to-end, where it previously failed atdatasets-live.jl:70(BlobTree upload). The flag has existed in rclone since v1.55 (2021), so no compat impact.Pairs with JuliaComputing/JuliaHub#22217 (server-side fix that broadens the BlobTree session policy to also authorize the bare
<version>key); either alone resolves the failure but together they're defense in depth.