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

Move info- back to the front of .conda for limited range request web servers #276

Open
2 tasks done
dholth opened this issue Dec 2, 2024 · 0 comments
Open
2 tasks done
Labels
type::feature request for a new feature or capability

Comments

@dholth
Copy link
Contributor

dholth commented Dec 2, 2024

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Move info- to the front of the .conda archive in case a web server does not support range requests.

It was moved to the back for streaming create or transmute, but "knowing the full size before starting zstandard compression to limit RAM usage on decompression" turned out to be more important than avoiding temporary files on compression.

Why is this needed?

No response

What should happen?

No response

Additional Context

Python's zipfile always needs to see the end of the .conda for the directory, however there are specialized streaming zip libraries that can do an okay job reading item headers without the central directory.

@dholth dholth added the type::feature request for a new feature or capability label Dec 2, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature request for a new feature or capability
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant