Update bastion-executor requirement from 0.3.5 to 0.4.0

[dependabot-preview]

Updates the requirements on bastion-executor to permit the latest version.

Release notes

Sourced from bastion-executor's releases.

Bastion v0.4.0

Getting Started | Examples | API documentation

What is new?

This release is coming with exciting features:

• Agnostik executor runtime
  • With Agnostik, Bastion can run on any runtime. Head over to the agnostik project for more information.
• Nuclei , an agnostic proactive IO system
  • With nuclei and agnostik, IO and executors are separated.
  • You can mix and match any executor with agnostik and use the same IO system.
  • Nuclei is based on Proactive IO.
  • Nuclei supports io_uring and works well with completion based evented IO. Windows support is currently in the works.
  • Completely async, can be independently used from Bastion.
    • It will power Bastion’s IO system and ecosystem.
• Autoscaling feature for actors
  • Right now with the scaling feature enabled, you can create actor groups in Bastion that will adapt to incoming workload according to given resizer parameters.
  • Example construction is like:

    children
        .with_redundancy(3) // Start with 3 actors
        .with_heartbeat_tick(Duration::from_secs(5)) // Do heartbeat each 5 seconds
        .with_resizer(
            OptimalSizeExploringResizer::default()
                .with_lower_bound(1) // A minimal acceptable size of group
                .with_upper_bound(UpperBound::Limit(10)) // Max 10 actors in runtime
                .with_upscale_strategy(UpscaleStrategy::MailboxSizeThreshold(3)) // Scale up when a half of actors have more than 3 messages
                .with_upscale_rate(0.1) // Increase the size of group on 10%, if necessary to scale up
                .with_downscale_rate(0.2), // Decrease the size of group on 20%, if there are too many idle actors
        )

• Cluster/distributed actors
  • After some extensive testing of the Artillery protocol, we are super thrilled to show SWIM based epidemic cluster for Bastion. (SWIM stands for ****Scalable Weakly-consistent Infection-style Membership, we know it’s a mouthful, visit this blog post if you would like an introduction https://asafdav2.github.io/2017/swim-protocol/). You can see example code for cluster execution in here: https://github.com/bastion-rs/showcase/tree/master/bastion-cluster
  • You can see a ping pong cluster example here: https://twitter.com/vertexclique/status/1273945945126973440
• Named child in children groups
  • Right now you can get the names of the child in children groups. You can use that for logging or anything that comes to mind.
  • With this enabled everything is user readable content addressable in Bastion runtime.
• Heartbeat for children
  • Now runtime continuously watches children with heartbeat to check their status and do sampling over their internals.
  • This feature doesn’t require any feature flags.
  • Used in scaling example as seen above:

    children
        .with_heartbeat_tick(Duration::from_secs(5)) // Do heartbeat each 5 seconds

• Dispatchers allow you to route specific messages to specific groups and collect messages from them.
  • This enables creating various fan-outs and fan-ins, and streaming data processing implementations.
  • An example of dispatcher system can be found in: https://github.com/bastion-rs/bastion/blob/master/src/bastion/examples/round_robin_dispatcher.rs#L4
• Dead letters mailbox so undelivered messages can be processed or monitored later on.

Changelog

Sourced from bastion-executor's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

Generated by auto-changelog.

v0.3.4 - 2020-01-29

Merged

• Roll bastion 0.3.4 [#164](https://github.com/bastion-rs/bastion/issues/164)
• Removed Pool::recover_async_thread method [#163](https://github.com/bastion-rs/bastion/issues/163)
• Remove debug statements in lightproc code [#162](https://github.com/bastion-rs/bastion/issues/162)
• Changelog config [#161](https://github.com/bastion-rs/bastion/issues/161)
• Update futures-timer requirement from 2.0.2 to 3.0.0 [#160](https://github.com/bastion-rs/bastion/issues/160)
• Use actions/checkout@master in Clippy check [#159](https://github.com/bastion-rs/bastion/issues/159)
• Max retries support for existing restart strategies [#157](https://github.com/bastion-rs/bastion/issues/157)
• Implemented linear/exponential back off recovery strategy [#156](https://github.com/bastion-rs/bastion/issues/156)
• Stateful ProcStack [#149](https://github.com/bastion-rs/bastion/issues/149)
• bastion-utils: Add missing readme reference to cargo.toml [#153](https://github.com/bastion-rs/bastion/issues/153)
• Add macros to instantiate children and supervisors [#140](https://github.com/bastion-rs/bastion/issues/140)
• Fix extreme amount of syscalls to give time share to OS [#147](https://github.com/bastion-rs/bastion/issues/147)
• Split children into four modules: children, children_ref, child, child_ref [#144](https://github.com/bastion-rs/bastion/issues/144)
• Use original GitHub actions [#142](https://github.com/bastion-rs/bastion/issues/142)
• Configurable thread count and thread pinning [#141](https://github.com/bastion-rs/bastion/issues/141)
• Fix warnings [#132](https://github.com/bastion-rs/bastion/issues/132)
• Message Signature to identify message sender and sending messages back [#130](https://github.com/bastion-rs/bastion/issues/130)
• Update crossbeam-utils requirement from 0.6 to 0.7 [#136](https://github.com/bastion-rs/bastion/issues/136)
• Update crossbeam-epoch requirement from 0.7 to 0.8 [#135](https://github.com/bastion-rs/bastion/issues/135)
• Update windows datatypes [#129](https://github.com/bastion-rs/bastion/issues/129)
• EMA based statistically adaptive blocking thread pool [#127](https://github.com/bastion-rs/bastion/issues/127)
• Bump bastion-executor dependency to 0.3.2-alpha.0 [#126](https://github.com/bastion-rs/bastion/issues/126)
• Fix link and remove empty doc [#124](https://github.com/bastion-rs/bastion/issues/124)
• Add Bastion::spawn method [#122](https://github.com/bastion-rs/bastion/issues/122)
• Replaced "futures-preview" with "futures" [#120](https://github.com/bastion-rs/bastion/issues/120)
• Ignore migration path under lock contention [#115](https://github.com/bastion-rs/bastion/issues/115)
• Fix doc links and middleware example [#114](https://github.com/bastion-rs/bastion/issues/114)
• Stat sampler improvements [#113](https://github.com/bastion-rs/bastion/issues/113)
• [executor] Fetch cores at once, rely on runtime [#112](https://github.com/bastion-rs/bastion/issues/112)
• Updated msg! to allow explicit and implicit returns [#111](https://github.com/bastion-rs/bastion/issues/111)
• Fixed children redundancy tests [#108](https://github.com/bastion-rs/bastion/issues/108)
• Removed all unsafe code from "bastion" [#107](https://github.com/bastion-rs/bastion/issues/107)
• Updated the changelog. [#106](https://github.com/bastion-rs/bastion/issues/106)
• Removed the "qutex" patch [#99](https://github.com/bastion-rs/bastion/issues/99)
• Added env_logger to all bastion's examples. [#98](https://github.com/bastion-rs/bastion/issues/98)
• Cleaned up bastion-executor [#97](https://github.com/bastion-rs/bastion/issues/97)
• Updated the documentation for BastionContext [#96](https://github.com/bastion-rs/bastion/issues/96)

Commits

• a792ad8 Bump towards 0.4.0
• 2b6c4b5 Make a move
• 1bcf602 Some readme rewording
• ba909f6 Reword readme
• 455c361 (cargo-release) start next development iteration 0.3.7-alpha.0
• cec6d83 (cargo-release) version 0.3.6
• 9ab79e2 Don't building examples automatically
• 72e9feb (cargo-release) start next development iteration 0.3.6-alpha.0
• 4415dff readme not read
• 26c3693 (cargo-release) version 0.3.5
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #41.