orchestra issueshttps://gitlab.inria.fr/apere/orchestra/-/issues2019-10-03T11:34:19+02:00https://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.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.