Age | Commit message (Collapse) | Author |
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Because we didn't pin the dependency in Cargo.toml, a `cargo update` or fresh
build resulted in beta.4 being used and fails because a new feature was
introduced in newer compilers.
Hence, pin the clap version to exactly this version for now.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
A quick test showed that the parallel approach here reduced the loading time by
approx 10%.
Not good, but better than before.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
Tested-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
dialoguer depends on zeroize, which broke their public interface in 1.4.0 by
updating the minimum required rust version to 1.51.0.
Because we have 1.50.0, this does not work anymore.
Because dialoguer depends on zeroize "1.1.1", we can pin zeroize to 1.3 in our
dependencies, to force the build to not use the 1.4.* release (or newer) of
zeroize.
This is of course not a long-term solution. The proper fix is to update our
MSRV, but I do not want to do that right before our 0.2.0 release.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Because the 4.0.0 contained a bug which was fixed (by us!) in
https://github.com/sunng87/handlebars-rust/pull/445
we must use 4.0.1 as minimum version requirement.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
Tested-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
|
|
Because the update broke interpolation of the "patches" variable from the
package definitions (and possibly others), we revert the update for now until we
figured out what is actually wrong here.
This reverts commit 3cb481417b13c5664bb4157d932b8ad4df5cb66d.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
Tested-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
This should reduce our dependencies by a certain number.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
0.16.1 has been published which fixes the bug introduced by 0.16.0, hence update
this dependency.
This reverts commit ddbd9629b3188c9f08d023829683c40ab9e1448b.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
This reverts the dependency update because indicatif 0.16 introduced a
reachable `unreachable!()` statement in their sourcecode that we
actually hit if we `--hide-bars`.
This reverts commit 6ceccb679d9c2d19389c6c6eef792d8db9086f31.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
The automatic pager setup resulted in more confusion in using the CLI than in
benefit. Hence, remove this feature again.
This reverts commit b5a3f02a05311d5f5a4eb35b8d2513cb6a543560.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
|
|
Because the interfaces of indicatif have changed, this PR changes a lot of
calls in the codebase. (Yay, moving all the things!)
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
|
|
This patch adds automatic pager setup in some of the subcommand implementations.
The "build" subcommand is explicitely not added here.
The setup is also done in a helper function to be able to alter the setup in one
place.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
This patch adds a human-panic so that we get nice bug reports if an user
experiences a crash of butido.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
See also:
https://rustsec.org/advisories/RUSTSEC-2021-0037.html
https://github.com/diesel-rs/diesel/pull/2663
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
See:
https://rustsec.org/advisories/RUSTSEC-2018-0002.html
https://github.com/alexcrichton/tar-rs/pull/156
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Aquamarine has been updated to support offline mode in 0.1.8, and
doesn't require internet connection to build and view the rendered
diagrams anymore.
This change switches from pinned patch version to a the 0.1 branch in
order to include the offline more feature and other backward-compatible
improvements coming in future
Signed-off-by: mersinvald <me@mkl.dev>
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
This is because the "sha1" crate seems to be unmaintained (no release in 3
years) but the sha-1 crate seems to be actively maintained in the context of a
bigger rust-crypto-functions project.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Tested-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
|
|
|
|
This patch rewrites patch post-processing with a new setter in the config-rs
crate:
Config::set_once()
That is introduced on a PR I've written for the crate.
The PR: https://github.com/mehcode/config-rs/pull/172
The new function is more likely to land on the config-rs master branch than the
old one, as it does not introduce more exported types from the config-rs crate.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
Tested-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
This patch ensures that pathes for patches are always relative to the repository
root, when loading the packages layered from the repository.
The problem is well described in the comment in the code, so this commit message
ends here.
This patch was written using an proposed feature for the config-rs dependency:
https://github.com/mehcode/config-rs/pull/165
This PR added a `Config::get_value_mut()` function and exported the
`config::value::ValueKind` type in config-rs public API.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
Tested-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
We need the "time" feature in tokio, because we want to implement pinging with a
wait time between the pings.
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
This forces the transitive dependency of "bitvec", named "funty", to 1.1.0.
Rationale:
https://github.com/bitvecto-rs/bitvec/issues/105#issuecomment-778570981
Signed-off-by: Matthias Beyer <matthias.beyer@atos.net>
|
|
This patch reimplements the package orchestration functionality to rely
on a DAG rather than a tree.
A
/ \
B E
/ \ \
C D F
Before this change, the structure the packages were organized in for a
build was a tree.
That did work reasonable well for initial development of butido, because
this is a simple case and the implementation is rather simple, too.
But, packages and their dependencies are not always organized in a tree.
Most of the time, they are organized in a DAG:
.-> C -,
/ \
D > A
\ /
`-> B -ยด
This is a real-world example: A could be a common crypto-library that I
do not want to name here.
B and C could be libraries that use the said crypto-library and D could
be a program that use B and C.
Because said crypto-library builds rather long, building it twice and
throwing one result away is a no-go.
A DAG as organizational structure makes that issue go away entirely.
Also, we can later implement checks whether the DAG contains multiple
versions of the same library, if that is undesireable.
The change itself is rather big, frankly because it is a non-trivial
change the replace the whole data structure and its handling in the
orchestrator code.
First of all, we introduce the "daggy" library, which provides the DAG
implementation on top of the popular "petgraph" library.
The package `Tree` datastructure was replaced by a package `Dag`
datastructure. This type implements the heavy-lifting that is needed to
load a package and all its dependencies from the `Repository` object.
The `JobTree` was also reimplemented, but as `daggy::Dag` provides a
convenient `map()` function, its implementation which transforms the
package `Dag` into a job `Dag` is rather trivial.
`crate::job::Dag` then provides the convenience `iter()` function to
iterate over all elements in the DAG and providing a `JobDefinition`
object for each node.
The topology in which we traverse the DAG is not an issue, as we need to
create tasks for all `JobDefinition`s anyways, so we do not care about
traversal topology at all.
The `crate::package::Package` type got an `Hash` implementation, which
is necessary to keep track of the mappings while reading the DAG from
the repository.
The implementation does not create the edges between the nodes in the
DAG right when inserting, but afterwards.
To keep track of the `daggy::NodeIndex`es, it keeps a mapping
Package -> NodeIndex
in a Hashmap. Thus, `Package` must implement `std::hash::Hash`
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Tested-by: Matthias Beyer <mail@beyermatthias.de>
squash! Reimplement as DAG
|
|
Because tokio 1.0 does not ship with the Stream trait, this patch also
introduces tokio_stream as new dependency.
For more information, look here:
https://docs.rs/tokio/1.0.3/tokio/stream/index.html
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
We don't need resiter::Map here anymore because itertools 0.10 provides
a map_ok() extension.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|