hydroflow_cli_integration v0.5.1
New Features
-
auto-configure Hydro Deploy based on Hydroflow+ plans
-
add initial test using Hydro CLI from Hydroflow+
This also required a change to Hydroflow core to make it possible to run the dataflow itself on a single thread (using a LocalSet), even if the surrounding runtime is not single-threaded (required to work around deadlocks because we can't use async APIs inside Hydroflow+). This requires us to spawn any Hydroflow tasks (only fordest_sink
at the moment) right next to when we run the dataflow rather than when the Hydroflow graph is initialized. From a conceptual perspective, this seems more right, since now creating a Hydroflow program will not result in any actual tasks running.In the third PR of this series, I aim to add a new Hydroflow+ operator that will automate the setup of a
dest_sink
/source_stream
pair that span nodes. -
split Rust core from Python bindings
Pre-Move Commit Statistics
- 2 commits contributed to the release over the course of 3 calendar days.
- 169 days passed between releases.
- 2 commits were understood as conventional.
- 2 unique issues were worked on: #978, #982
Chore
- manually set lockstep-versioned crates (and
lattices
) to version0.5.1
Setting manually since
frewsxcv/rust-crates-index#159 is messing with
smart-release - generate pre-move changelogs for
hydro_cli
andhydroflow_cli_integration
Pre-Move Commit Details
view details
Commit Statistics
- 3 commits contributed to the release over the course of 39 calendar days.
- 209 days passed between releases.
- 3 commits were understood as conventional.
- 2 unique issues were worked on: #1046, #986