Casper da Costa-Luis
Casper da Costa-Luis
@bmabir17-asj do you mean NVIDIA/nvidia-docker#860? Is it still an issue for you?
the other way around. Need to replace https://github.com/search?q=org%3Aiterative+peter-evans&type=code with CML.
Do we need to action some things though? - update some FAQ in the docs? - improve the CLI error message #606? - fix & merge #1003?
this can be merged with #908, right?
> Lazy experiment pull and apply don't see much of a problem with e.g. `dvc exp pull && dvc exp apply || dvc exp run`
> > Lazy experiment pull and apply > > don't see much of a problem with e.g. `dvc exp pull && dvc exp apply || dvc exp run` btw @0x2b3bfa0...
potential workflow: ```bash dvc exp run --name JOB_ID_UNCHANGED_UPON_KILL_AND_RESTART --pull # ... (auto)kill via SIGINT after ~72h ... # CML does this 5 min early dvc exp push # CML does...
Should add docs to https://cml.dev/doc before resolving? Also maybe some tests?
@DavidGOrtega since there are lots of approaches I'd suggest writing CLI docstrings for your ideas so we can discuss them before spending time implementing a polished PR.
looks like https://github.com/AndreMiras/coveralls-python-action is a viable replacement for `coverallsapp/github-action` (and https://github.com/AndreMiras/coveralls-python-action/pull/5 will even allow parallel builds).