-
Notifications
You must be signed in to change notification settings - Fork 80
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
replace piz with rc-zip #3012
base: latest
Are you sure you want to change the base?
replace piz with rc-zip #3012
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## latest #3012 +/- ##
==========================================
- Coverage 87.99% 87.94% -0.05%
==========================================
Files 136 137 +1
Lines 22230 22214 -16
Branches 2225 2225
==========================================
- Hits 19561 19536 -25
- Misses 2356 2365 +9
Partials 313 313
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
bd9556b
to
0072045
Compare
What do we need in order to switch to 1.74? Is it just time, other packages, etc? |
We don't really have any rules, but I usually check
1.74 was released Nov 16th, which is fairly recent for distro standards/release cycles. 1.74 is also a pretty big release due to projections in opaque return types, which is exactly the feature that Maybe a good rule of thumb is checking what rust is available on the places we do packaging:
But these are fairly fast moving places =] More links:
|
7aaa1a8
to
37343ec
Compare
(asking here, because it's relevant to some memory questions) - how are we feeling about Rust 1.74 these days? |
I've been using https://lib.rs/stats#rustc-usage to check MSRV bumps, 1.74 would put us in 96-97% of all crates.io requests. 1.74 was released November 16, 2023, so I think it is OK to bump MSRV. |
37343ec
to
bda11a5
Compare
rc-zip can work on top of regular files (not memmap-ed files like piz).
It is also much easier to interact with.
Pending: more perf tests, but mem-wise I ran the command from #1909 (comment) and was seeing ~110MB max memory consumption.
Sadly, I think this will be draft for quite some time, it needs Rust 1.74 to compile =/
(it also broke wasm, need to do some splitting in
src/core/src/storage.rs
to be able to compile a subset...)