You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently looked at this and my understanding is that range request happens via http Headers, and Bazel is currently propagating these headers through a set of remote asset API qualifiers?
If that's the case, #301 could be relevant because the majority of the Remote Asset APIs don't support Bazel's custom qualifiers but don't report errors when these qualifiers are requested.
This issue is a follow-up to bazelbuild/bazel#22207, which has more context on the motivation and need for range downloads
I'm using https://github.com/chainguard-dev/rules_apko, which depends on range downloads. In bazel >7.1, this is achieved by setting the headers attr.
The remote download APIs currently don't support range downloads, so I can't use
rules_apko
in my bazel workspace.The text was updated successfully, but these errors were encountered: