[bug] Multi-Repo Tome Imports File Conflicts

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
go, graphql, rust
领域
backend, devtools

调研方向

The issue is a design conflict when two imported repos share a tome and the same asset name, so imports overwrite each other. Read how tomes reference assets by name and how multi-repo imports currently land files. Decide between namespacing (which breaks agent lookups) versus sending an id-to-name mapping so fetches use ids. Done means imports no longer clobber assets and agents can still resolve them; there is no named file or test in the issue.

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

描述

bug help wanted

Describe the bug
If two repos have the same tome, with the same asset, then they will conflict (and overwrite eachother each time they are imported). To solve this, we could prefix the name with a namespace (e.g. the imported repo), but this would prevent the agent from being able to access the asset (since the tome references assets by name, and they are not expected to know which repository they were imported from).

Additional context
It's possible that we could send a mapping of ids <--> asset names to the agent and always reference by id when fetching assets.

主要语言
Rust
星标
639
派生
65
平均合并
1 天 5 小时
30 天内合并 PR
62

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

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

spellshift/realm 的其他 Issue

查看 spellshift/realm 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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