orchestra issueshttps://gitlab.inria.fr/apere/orchestra/-/issues2019-12-19T09:07:05+01:00https://gitlab.inria.fr/apere/orchestra/-/issues/35Enhances some error messages2019-12-19T09:07:05+01:00PERE AlexandreEnhances some error messagesErrors messages could be changed in the following cases:
+ The `.orchestra` folder does not exist.
+ The remote directory where to put the files does not exist either.Errors messages could be changed in the following cases:
+ The `.orchestra` folder does not exist.
+ The remote directory where to put the files does not exist either.V0.4.0https://gitlab.inria.fr/apere/orchestra/-/issues/27Website2019-10-03T11:36:39+02:00PERE AlexandreWebsiteCreate a small hosted website explaining how runaway works.Create a small hosted website explaining how runaway works.V0.4.0https://gitlab.inria.fr/apere/orchestra/-/issues/10Refine developer documentation2019-09-06T10:32:36+02:00PERE AlexandreRefine developer documentationWalk through all the documentation, check that everything is still valid, give more details about asynchronous implementation.Walk through all the documentation, check that everything is still valid, give more details about asynchronous implementation.V0.3.0https://gitlab.inria.fr/apere/orchestra/-/issues/7Orchestra with new backend2019-10-03T11:37:01+02:00PERE AlexandreOrchestra with new backendReimplement `orchestra` with the new `liborchestra`.Reimplement `orchestra` with the new `liborchestra`.V0.4.0https://gitlab.inria.fr/apere/orchestra/-/issues/4Profile installation scripts2019-10-03T11:37:12+02:00PERE AlexandreProfile installation scriptsWe should provide assisted installation scripts rather than templates that must be changed by the user himself.We should provide assisted installation scripts rather than templates that must be changed by the user himself.V0.4.0https://gitlab.inria.fr/apere/orchestra/-/issues/2Tutorial explaining profile writing2019-10-03T11:37:28+02:00PERE AlexandreTutorial explaining profile writingWe should include a tutorial that explains how to specify a profile.We should include a tutorial that explains how to specify a profile.V0.4.0https://gitlab.inria.fr/apere/orchestra/-/issues/36Tar command does not accept enough arguments.2019-12-19T09:13:04+01:00PERE AlexandreTar command does not accept enough arguments.To unpack the data on the remote end, the tar command is given a list of files. Problem is when this list is too big, the system `ARG_MAX` limit is exceeded, and it fails to `execve`. One fix is to write the files to a file and give it a...To unpack the data on the remote end, the tar command is given a list of files. Problem is when this list is too big, the system `ARG_MAX` limit is exceeded, and it fails to `execve`. One fix is to write the files to a file and give it as arguments to tar.https://gitlab.inria.fr/apere/orchestra/-/issues/30Removing runaway subcommands in favor of a single `--sched` argument.2019-12-19T09:02:09+01:00PERE AlexandreRemoving runaway subcommands in favor of a single `--sched` argument.Since the batch subcommand is able to run a single exec, and sched is pretty much the same thing as batch, it would allow to reduce maintenance to a single command.Since the batch subcommand is able to run a single exec, and sched is pretty much the same thing as batch, it would allow to reduce maintenance to a single command.https://gitlab.inria.fr/apere/orchestra/-/issues/26Refactor error handling2019-10-03T11:34:19+02:00PERE AlexandreRefactor error handlingI took the approach of putting an error type within every submodules. Most of the errors can contain a String, which describe the error. Combination of errors is made through a lot of
```rust
map_err(|e| SomeError(format!("Module level...I took the approach of putting an error type within every submodules. Most of the errors can contain a String, which describe the error. Combination of errors is made through a lot of
```rust
map_err(|e| SomeError(format!("Module level error encountered: {}", e))
```
A simpler combination strategy could be found, since apart from the `liborchestra::hosts::provider`, error semantics is rarely used. We could add an `Unbounded` semantics, that would allow an easier combination of errors.