I wrote about this at length already. When you write uses: actions/checkout@v4, you’re declaring a dependency that GitHub resolves, downloads, and executes, and the runner’s PrepareActionsRecursiveAsync walks the tree by downloading each action’s tarball, reading its action.yml to find further dependencies, and recursing up to ten levels deep. There’s no constraint solving at all. Composite-in-composite support was added in 2021, creating the transitive dependency problem, and a lockfile was requested and closed as “not planned” in 2022.
This Tweet is currently unavailable. It might be loading or has been removed.
。新收录的资料对此有专业解读
可设置自动关闭时间，防止长期运行带来的风险。删除Sandbox后，所有数据完全清除。
尝试不同的 opset 或更新 PyTorch：有些导出器 bug 在较新 opset 或 PyTorch 版本里被修复。可试 opset_version=12、14 等；若可行，升级 PyTorch 往往能解决这类问题。