Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

MAX_PARTS is treated as universal, but it is not

未关闭
#389 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
cli

调研方向

Start at crates/s3/src/multipart.rs where MAX_PARTS is defined, then trace which commands (rc put, rc object copy) consume it. Decide where a configurable part limit belongs — CLI flag, config file, or auto-detected bucket capability — and check how other S3 client settings are threaded through the CLI. Done means a user can raise or lower the multipart part ceiling for uploads without recompiling, with tests covering a non-1000 limit such as Scaleway's.

由索引模型根据 Issue 内容生成。

描述

In this code, MAX_PARTS is hard-coded to match AWS' S3 implementation: https://github.com/rustfs/cli/blob/main/crates/s3/src/multipart.rs#L19

This assumes that all S3 implementations have the same ceiling on number of parts. They do not. For example, Scaleway Object Storage is compatible with the S3 protocol, but limits multipart uploads to 1000 parts: https://www.scaleway.com/en/docs/object-storage/api-cli/multipart-uploads/

Would it be possible to make MAX_PARTS configurable in some way for CLI users?

I have concrete projects I am migrating from mc to rc, but cannot progress with this limitation. (Previously we used mc od which allowed part configuration, but it was always a bit of a bad solution, compared to having better built-in suport for setting max number of parts in all commands that use the field, e.g. rc put, rc object copy).

主要语言
Rust
星标
159
派生
23
平均合并
7 小时 4 分钟
30 天内合并 PR
10

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

rustfs/cli 的其他 Issue

查看 rustfs/cli 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。