mirror of https://github.com/rustfs/rustfs.git synced 2026-08-08 22:33:22 +00:00

Files

T

houseme f9874b591a [DO NOT MERGE until published] chore(ecstore): switch rustfs-uring to crates.io 0.1.0 (#4701 )

* chore(ecstore): switch rustfs-uring from the git rev to crates.io 0.1.0

Prepared ahead of the rustfs-uring 0.1.0 crates.io release (rustfs/uring):
flip ecstore's dependency from the pinned git revision to the published
`0.1.0`, and drop the now-unneeded git-source allowance in deny.toml.

DO NOT MERGE until rustfs-uring 0.1.0 is on crates.io. Until then cargo
cannot resolve `rustfs-uring = "0.1.0"`, so this branch will not build and
CI will be red — that is expected, not a defect in the change.

After the crate is published:
  1. `cargo update -p rustfs-uring --precise 0.1.0` to regenerate Cargo.lock
     (deliberately not touched here — the registry entry, with its checksum,
     cannot be written before the crate exists);
  2. push the Cargo.lock;
  3. CI goes green; merge.

No code change. The guard `scripts/check_no_tokio_io_uring.sh` is unaffected
(it bans only tokio's io-uring runtime feature, not an explicit rustfs-uring
dependency). `audit.yml`'s `allow-dependencies-licenses` for rustfs-uring is
left in place — it is a first-party Apache-2.0 crate either way.

Co-Authored-By: heihutu <heihutu@gmail.com>

* chore: refresh rustfs-uring lockfile

---------

Co-authored-by: heihutu <heihutu@gmail.com>

2026-07-10 19:53:23 +00:00

benches

refactor: segment residual storage api boundaries (#3905 )

2026-06-26 15:56:38 +08:00

docs

refactor: use canonical Rust module paths (#4269 )

2026-07-05 03:01:14 +08:00

src

fix(object-data-cache): make the GET key write-unique and dedup the lookup (#4693 )

2026-07-10 18:22:20 +00:00

tests

test(interop): add real MinIO read and migration parity tests (#4377 )

2026-07-08 01:12:49 +08:00

AGENTS.md

chore(agents): add Rust code quality rules and skill (#3144 )

2026-05-31 22:19:36 +08:00

build.rs

refactor: Restructure project layout and clean up dependencies (#30 )

2025-07-02 19:33:12 +08:00

Cargo.toml

[DO NOT MERGE until published] chore(ecstore): switch rustfs-uring to crates.io 0.1.0 (#4701 )

2026-07-10 19:53:23 +00:00

README.md

fix: revert standalone #2351 artifacts (phase 5) (#2535 )

2026-04-14 22:35:05 +08:00

run_benchmarks.sh

fix(get): remove GET chunk fast path (#2507 )

2026-04-12 23:12:23 +08:00

README.md

RustFS ECStore - Erasure Coding Storage

High-performance erasure coding storage engine for RustFS distributed object storage

📖 Documentation · 🐛 Bug Reports · 💬 Discussions

📖 Overview

RustFS ECStore provides erasure coding storage capabilities for the RustFS distributed object storage system. For the complete RustFS experience, please visit the main RustFS repository.

✨ Features

Reed-Solomon erasure coding implementation
Configurable redundancy levels (N+K schemes)
Automatic data healing and reconstruction
Multi-drive support with intelligent placement
Parallel encoding/decoding for performance
Efficient disk space utilization

📚 Documentation

For comprehensive documentation, examples, and usage guides, please visit the main RustFS repository.

📄 License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Copyright 2024 RustFS Team

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

RustFS is a trademark of RustFS, Inc.
All other trademarks are the property of their respective owners.

Made with ❤️ by the RustFS Storage Team