No way to read a workflow without creating a build
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
从现有的 comfy build from-workflow 命令和 issue 中描述的 POST /v1/workflows/resolve endpoint 开始。跟踪 CLI 如何读取 workflow 并打印 build response，然后提供一个只读路径，用于报告 workflow definition 和 import report。当可以在不创建 build 的情况下检查不熟悉的 workflow 时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
comfy build from-workflow is the only verb that reads a workflow file, and it creates a build as a side effect. There is no way to ask what a workflow contains first.
The builder already serves the read-only door. POST /v1/workflows/resolve returns the same definition and report and creates nothing; its own description says it is "for a caller that wants to show a person what the workflow means first". The CLI exposes only the create door.
Why it matters: an agent handed an unfamiliar workflow is told to describe what will be created before creating it, and cannot. It has to write a build to find out whether the build is worth writing. On a graph carrying a class nobody publishes, that record is pure litter: the definition comes back {} and the right answer is not to build at all.
Observed, staging, a workflow with one unpublishable class:
$ comfy build from-workflow --from sdxl-with-unknown.json --name probe
{"ok": true, "data": {"build": {"id": "b0fed96c-...", "definition": {},
"workflowImportReport": {"unresolvedClasses": ["TotallyMadeUpNodeXYZ42"], ...}}}}
A build now exists that should never have been created, and the only way to have known that was to create it.
Suggested: a comfy build resolve-workflow --from <file> (or --dry-run on from-workflow) that posts to /v1/workflows/resolve and prints the report without writing anything.
Found while testing the comfy-build skill's workflow path end to end.
- 主要语言
- Python
- 星标
- 1k
- 派生
- 176
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 87
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Comfy-Org/comfy-cli 的其他 Issue
-
test_file_utils umask tests assert against a umask the code never reads (import-time _UMASK), so they only pass on a 0o022 host可能已有人在做 @neverbiasu 于 10 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
Comfy-Org/comfy-cli#907 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 92/100
Comfy-Org/comfy-cli#781 · 1 条评论 ·
维护者通常 1 天内回复
-
`comfy launch --background` fails with FileNotFoundError when comfy-cli is invoked by path可能已有人在做 @RaphaelFakhri 于 42 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
Comfy-Org/comfy-cli#691 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
Comfy-Org/comfy-cli#670 · 2 条评论 ·
维护者通常 1 天内回复
查看 Comfy-Org/comfy-cli 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 65/100
StevenBlack/hosts#3299 ·
-
`garak --report` overwrites the input report when its name has no ".report"可能已有人在做 @0z5a 今天认领。 未关闭needs-triage
难度 2/5 半天 新手友好度 72/100
维护者通常 2 天内回复
-
plot_graph crashes when a mesh node has no m2m edge可能已有人在做 @tygvi 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
mllam/neural-lam#883 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
future-agi/future-agi#4092 · 1 条评论 ·
维护者通常 1 天内回复
-
transcript analytics: a text whose only protected spans the prose pass redacts is withheld whole未关闭
难度 1/5 1 小时以内 新手友好度 82/100
WingedGuardian/GENesis-AGI#4641 ·
维护者通常 1 天内回复