Repository navigation
fix: 默认使用原生 worktree 模式,--mode / FSC_EXECUTION_MODE 真正生效 - #11
Conversation
… now take effect - FSC_EXECUTION_MODE was never read by configReader, so `run --mode` was silently ignored and every run used docker regardless of the flag or --help text - default executionMode docker -> worktree, harnessMode docker -> local; docker stays optional - ExecutionMode type now includes "worktree" (was cast through any); invalid values throw - README execution-mode section rewritten around native worktree Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016FSVfwwP6TVxGLUWatWM53
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 13 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
问题
FSC 的 agent 是原生进程,不是 Docker 容器,但默认配置是
executionMode: docker,而且run --mode根本不生效:configReader没有读取FSC_EXECUTION_MODE,CLI 设置的环境变量被无声丢弃。帮助文字写默认bare,实际跑的是 docker。改动
executionMode改为worktree(原生 git worktree),harnessMode改为local;docker 保留为可选。configReader读取FSC_EXECUTION_MODE,非法值直接报错。ExecutionMode类型补上worktree,去掉as any。--mode默认值与说明对齐。验证
tsc --noEmit:退出码 0bun test:三次完整运行分别是 176 通过 0 失败、175 通过 1 失败、176 通过 0 失败。失败的是不同的计时类测试(UnifiedScheduler (MockScheduler)、CodeCommitter),本机同时有其他会话在跑,负载高;单独跑scheduler.test.ts三次均通过。未做根因排查,应视为偶发。🤖 Generated with Claude Code
https://claude.ai/code/session_016FSVfwwP6TVxGLUWatWM53