Define and enforce case-only name collision policy for GitHub server identities
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go, postgresql
调研方向
Start by tracing the persistence path that keys versions and publish locks by server_name, then inspect the database constraints and tests around publishing. Audit existing io.github.* records and decide how uniqueness treats owner casing while preserving stored names; add coverage for legacy collisions, aliases, distinct owners, version updates, and concurrent publishes. Done means the chosen policy is enforced transactionally without changing other namespace behavior.
由索引模型根据 Issue 内容生成。
描述
Summary
Follow-up to #1788 and the discussion in #689.
GitHub user and organization identifiers are case-insensitive, while the Registry preserves mixed-case server names. #1788 addresses authorization by matching the GitHub owner portion of io.github.<owner>/* grants without regard to case. It deliberately does not canonicalize persisted server identities.
The persistence path currently keys versions and publish locks by the supplied server_name. Depending on the storage constraints and existing data, this can allow io.github.Foo/tool and io.github.foo/tool to become independent records, even though they refer to the same GitHub owner. Simply lowercasing existing names would break stable registry identities and existing publishers.
Proposed investigation / acceptance criteria
- Audit existing
io.github.*records for names that differ only by case before introducing a constraint; decide how existing collisions should be treated. - Specify which portions of a GitHub server name should be case-insensitive for uniqueness (owner only vs. complete name) without silently changing existing stored names or URL identities.
- Preserve the exact stored name across subsequent versions; avoid rewriting published records.
- Prevent publishing a new case-only alias for an existing identity, including concurrent publishes. Consider canonicalized advisory lock keys and a transaction-safe database constraint/check, not an application-only pre-check.
- Add tests covering legacy mixed-case records, new case-only aliases, distinct owners, normal version updates, and concurrent publication.
- Keep other namespace types' uniqueness/matching behavior unchanged unless explicitly designed otherwise.
Scope
This issue concerns storage-level identity and concurrency, not the publish authorization 403 resolved in #1788. As requested in the PR review, the storage policy should be considered separately rather than delaying that compatibility fix.
References: #689, #1788, #1623.
- 主要语言
- Go
- 星标
- 7.4k
- 派生
- 1k
- 平均合并
- 17 小时 57 分钟
- 30 天内合并 PR
- 68
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/registry 的其他 Issue
-
3 registry records that cannot resolve for any client, and a caution about single-pass dead counts未关闭
难度 2/5 1-3 小时 新手友好度 68/100
modelcontextprotocol/registry#1692 ·
维护者通常 1 天内回复
-
IsValidRemoteURL only blocks literal localhost/127.0.0.1 — misses [::1], 127.0.0.0/8, 0.0.0.0, and private/link-local addresses可能已有人在做 @amitvijapur 于 108 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/registry#1465 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 55/100
modelcontextprotocol/registry#1807 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 49/100
modelcontextprotocol/registry#1792 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 28/100
modelcontextprotocol/registry#1789 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/registry 的全部 Issue
相似的 Issue
-
[Bug] Custom tool truncation leaves unused stream copies open可能已有人在做 @OUAO-FRANK 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
[v3] KeyBindingManager calls (Add/Remove) are not converted into a case-insensitive accelerator.Key未关闭Bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
crmne/hyprmoncfg#114 · 1 条评论 ·
维护者通常 1 天内回复
-
runtime: usleep sleeps nanoseconds instead of microseconds on linux/mips and linux/mips64可能已有人在做 @BRobertson7 今天认领。 未关闭compiler/runtime
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100