Skip to content

Conversation

@NobodyXu
Copy link
Collaborator

About 170KB, not a lot for individual tarball but given how many downloads are made from crates.io it's indeed quite large

It can be seem as a kind of optimization for crates.io CDN and caching

IIRC another crate has done the same and some debian maintainers have complained about not being about to run test, but I can't remember which.

Not sure if our crate is on debian given that we don't even maintian MSRV

About 170KB, not a lot for individual tarball but given how many downloads are made it's indeed quite large

Signed-off-by: Jiahao XU <[email protected]>
@NobodyXu NobodyXu requested a review from robjtede August 23, 2025 12:05
@robjtede
Copy link
Member

robjtede commented Aug 23, 2025

Yea I've seen Debian and Nix packagers complain about this sort of thing in the past. Hmm.

@NobodyXu NobodyXu closed this Oct 2, 2025
@NobodyXu NobodyXu deleted the NobodyXu-patch-2 branch October 2, 2025 14:24
@NobodyXu
Copy link
Collaborator Author

NobodyXu commented Oct 2, 2025

Closing since we probably don't want to break the debian/nix packaging system

@codecov
Copy link

codecov bot commented Oct 2, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (776b25f) to head (1ab788a).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files
@@     Coverage Diff     @@
##   main   #376   +/-   ##
===========================
===========================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants