Run the exe.dev Worker with SSH children on a real VM

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
github, typescript
领域
devops, testing

调研方向

Start with the test:exe-dev integration test in packages/orchestrator and the SSH stand-in at packages/agents/test/fixtures/ssh-shim.sh; configure the four USINE_EXE_DEV_INTEGRATION_* values to run it against a real Worker VM. Check Claude and Codex child execution, GitHub host access, pid file cleanup, restart recovery, cancellation, and the wall-clock ceiling. Done means those behaviors pass on a real VM, including stopping remote children before removing the worktree.

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

描述

#176 step 3 moved the exe.dev Worker's Pi parent into the orchestrator and runs Claude Code and Codex children on the VM over SSH. It is covered by unit tests with a fake SSH client and by the Claude and Codex live contracts through a local SSH stand-in (packages/agents/test/fixtures/ssh-shim.sh), which run the real CLIs and the real Agent SDK custom spawner. It has not run against a real exe.dev VM.

To check on a real Worker:

  • pnpm --filter @usine/orchestrator test:exe-dev with USINE_EXE_DEV_INTEGRATION_WORKER, USINE_EXE_DEV_INTEGRATION_REPO, USINE_EXE_DEV_INTEGRATION_REVISION, and USINE_EXE_DEV_INTEGRATION_GITHUB_INTEGRATION set (the test now provides the durable AttemptRuntime and expects a child session in the transcript).
  • A Claude child and a Codex child on the VM: the remote command line through the VM user's login shell, GH_HOST=github.int.exe.xyz reaching gh inside the child, the pid file <worktree>.child-<n>.pid present while the child runs and gone after.
  • An orchestrator restart mid-Attempt: the Attempt reattaches to the VM worktree, children from before the restart are stopped, and the parent delegates again.
  • Cancel and a wall-clock ceiling: remote children are stopped before the worktree is removed.
主要语言
TypeScript
星标
1
派生
0
平均合并
4 小时 26 分钟
30 天内合并 PR
280

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

basaltbytes/usine 的其他 Issue

查看 basaltbytes/usine 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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