Conversation editor never revokes blob URLs of removed attachments
维护者通常 2 天内回复
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 领域
- frontend
调研方向
Start with ChatInputArea.changeAttachments, which already revokes dropped blob URLs, and compare it with useConversationDraft.changeAttachments, which the ConversationEditor piece editor calls without revoking anything. The attachment chip URLs are created in PromptEditor with URL.createObjectURL. Done means removing an attachment in the draft editor calls URL.revokeObjectURL right away. Pull request #3186 is already open against this issue, so review or build on that work rather than starting a parallel fix.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
In the conversation editor, removing an attachment from a media piece never revokes the attachment's blob object URL. The blob: URL and its File payload stay alive until the whole draft is discarded or the editor unmounts.
ChatInputArea.changeAttachments handles the same removal correctly by revoking dropped blob URLs, but the draft editor path (ConversationEditor piece editor calling useConversationDraft.changeAttachments) forwards the new attachment list straight through with no revocation. Attaching and removing a large file repeatedly during one editing session pins every dropped File in memory.
Steps/Code to Reproduce
- Open a conversation in the editor and pick a media piece.
- Attach a file (the attachment chip gets a
blob:URL fromURL.createObjectURLin PromptEditor). - Remove the attachment with the chip's dismiss button.
URL.revokeObjectURLis never called for that URL until the draft is discarded or the editor unmounts.
Repeat 2-3 in one session and the dropped Files accumulate.
Expected Results
Removing an attachment in the editor revokes its blob object URL immediately, the same way the chat composer does.
Actual Results
The URL stays valid and the File payload stays pinned until the draft is discarded or unmounted.
Screenshots
N/A
Versions
OS: macOS
Browser: Chrome
Python version: 3.14
PyRIT version: installed from main (66c41fa)
- 主要语言
- Python
- 星标
- 4.6k
- 派生
- 944
- 平均合并
- 2 天 17 小时
- 30 天内合并 PR
- 328
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/PyRIT 的其他 Issue
-
BUG: SQLInjectionOutputScorer misses standard inline comment bypasses ('-- and ' OR 1=1--)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
microsoft/PyRIT#3204 · 1 条评论 ·
维护者通常 2 天内回复
-
BUG: label queries only return the final conversation of an attack可能已有人在做 @u7k4rs6 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
microsoft/PyRIT#3095 · 4 条评论 · 已指派 1 人 ·
维护者通常 2 天内回复
-
BUG Configuration keeps runtime-status errors after polling recovers可能已有人在做 @joeyvictorino 于 4 天前认领。 未关闭Bug: triage GUI help wanted
难度 2/5 1-3 小时 新手友好度 86/100
microsoft/PyRIT#2868 · 4 条评论 · 已指派 1 人 ·
维护者通常 2 天内回复
-
BUG: HTTPTarget sends conflicting Content-Length and Transfer-Encoding headers可能已有人在做 @Kaap10 于 9 天前认领。 未关闭Bug: triage
难度 2/5 1-3 小时 新手友好度 35/100
microsoft/PyRIT#3202 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 3/5 半天 新手友好度 25/100
维护者通常 2 天内回复
相似的 Issue
-
good first issue
难度 2/5 1-3 小时 新手友好度 85/100
btclib-org/btclib-node#1955 ·
维护者通常 1 天内回复
-
documentation v0.9.2
难度 2/5 半天 新手友好度 72/100
khuisman/mcp-gee-sweet#1033 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
ossf/cve-bin-tool#5966 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 2 天内回复
-
write_iceberg ignores the table's write.parquet.compression-codec property可能已有人在做 @YuangGao 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
Eventual-Inc/Daft#7606 ·
维护者通常 1 天内回复