Zhanghao Wu
Zhanghao Wu
> Is there a way to disable this feature (via the Python API) to produce the existing behavior? We use SkyPilot within the code running on the launched cluster, so...
> That would work! Will the command runner allow specifying a conda environment to run in? Currently, we decide not to have the argument for the command runner to make...
Another user requested for this PR: > it would be great if sky's core setup is less easily interfered by user's actions
master ([823999a](https://github.com/skypilot-org/skypilot/commit/823999af850ee93138f45d01abba6c54a93d3c1e)) ``` 2m2.152s 1m54.330s 1m57.132s 1m56.134s 1m49.895s ``` mean: 1m55.9286s [ae84211](https://github.com/skypilot-org/skypilot/pull/2801/commits/ae8421100d7e40e1a29ee5619b45c476e4ed16b8): `for i in {1..5}; do time sky launch -c test-gcp-$i --cloud gcp --cpus 2 -y; done` ``` 2m27.360s...
Closing this, as it is moved to #3575
This can be resolved by moving `num_nodes` into `resources`.
Running into this again for setting up slurm across nodes. The following can be a simplified version for a barrier that waits for head to be ready: ``` # Define...
cc'ing @cblmemo
Yes, either add a link there or embedded in the existing machines page. Otherwise, it is pretty hard to find that `local up` page.
> If you want to ssh from the head to the other workers and have it work for `mpirun`, its sufficient to enable `ssh-agent`. No need to setup/copy keys. I...