Bumps [array-init-cursor](https://github.com/planus-org/planus) from
0.2.0 to 0.2.1.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/planus-org/planus/blob/main/CHANGELOG.md">array-init-cursor's
changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<p>All notable changes to this project will be documented in this
file.</p>
<p>The format is based on <a
href="https://keepachangelog.com/en/1.0.0/">Keep a Changelog</a>,
and this project adheres to <a
href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p>
<h2>[Unreleased]</h2>
<h3>Added</h3>
<h3>Fixed</h3>
<h3>Removed</h3>
<h2>[1.1.1] - 2025-03-02</h2>
<h3>Added</h3>
<h3>Fixed</h3>
<ul>
<li>[Rust]: Fix the alignment of structs in unions <a
href="https://redirect.github.com/planus-org/planus/pull/289">#289</a></li>
</ul>
<h3>Removed</h3>
<h2>[1.1.0] - 2025-03-02</h2>
<h3>Added</h3>
<ul>
<li>Bump the Minimum Support Rust Version (MSRV) to 1.75.0</li>
<li>The <code>Primitive</code> and <code>VectorWrite</code> traits are
now marked as unsafe to remind implementers of alignment
constraints</li>
<li>[Rust]: Add support for union vectors <a
href="https://redirect.github.com/planus-org/planus/pull/287">#287</a></li>
<li>Add support for displaying union vectors with <code>planus
view</code> <a
href="https://redirect.github.com/planus-org/planus/pull/287">#287</a></li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Added extra unsafe blocks to templates to fix warnings for the 2024
edition</li>
<li>Updated tests for the 2024 edition</li>
</ul>
<h3>Removed</h3>
<h2>[1.0.0] - 2024-09-29</h2>
<h3>Added</h3>
<ul>
<li>[Rust]: Added <code>#[allow(dead_code)]</code> to the root of the
generated rust code <a
href="https://redirect.github.com/planus-org/planus/pull/204">#204</a></li>
<li>Added the option <code>ignore_docstring_errors</code> to the app. <a
href="https://redirect.github.com/planus-org/planus/pull/216">#216</a></li>
<li>Get rid of dependency on <code>atty</code> and bump the Minimum
Support Rust Version (MSRV) to 1.70.0. <a
href="https://redirect.github.com/planus-org/planus/pull/220">#220</a></li>
<li>[Rust]: Allow default implementations to be generated for tables
that have fields with (required) vectors, strings, integers and bools.
<a
href="https://redirect.github.com/planus-org/planus/pull/243">#243</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="be6f99afde"><code>be6f99a</code></a>
Add a soundness fix for array-init-cursor (<a
href="https://redirect.github.com/planus-org/planus/issues/294">#294</a>)</li>
<li><a
href="1cf18d16af"><code>1cf18d1</code></a>
Release 1.1.1 (<a
href="https://redirect.github.com/planus-org/planus/issues/290">#290</a>)</li>
<li><a
href="e1928da42c"><code>e1928da</code></a>
Fix alignment of large structs in unions (<a
href="https://redirect.github.com/planus-org/planus/issues/289">#289</a>)</li>
<li><a
href="060ffc788a"><code>060ffc7</code></a>
Release version 1.1.0 (<a
href="https://redirect.github.com/planus-org/planus/issues/288">#288</a>)</li>
<li><a
href="d96b907d3f"><code>d96b907</code></a>
Implement union vectors (<a
href="https://redirect.github.com/planus-org/planus/issues/287">#287</a>)</li>
<li><a
href="08d8c012a5"><code>08d8c01</code></a>
Small fixes (<a
href="https://redirect.github.com/planus-org/planus/issues/286">#286</a>)</li>
<li><a
href="b8129d7691"><code>b8129d7</code></a>
Mark <code>Primitive</code> and <code>VectorWrite</code> as unsafe (<a
href="https://redirect.github.com/planus-org/planus/issues/280">#280</a>)</li>
<li><a
href="b5d9d8194a"><code>b5d9d81</code></a>
Update the test suite (<a
href="https://redirect.github.com/planus-org/planus/issues/283">#283</a>)</li>
<li><a
href="4f04f66577"><code>4f04f66</code></a>
Add extra unsafe blocks as required by 2024 edition (<a
href="https://redirect.github.com/planus-org/planus/issues/282">#282</a>)</li>
<li><a
href="44ffb38190"><code>44ffb38</code></a>
New rust version, new clippy issues to fix</li>
<li>Additional commits viewable in <a
href="https://github.com/planus-org/planus/compare/v0.2.0...array-init-cursor-v0.2.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=array-init-cursor&package-manager=cargo&previous-version=0.2.0&new-version=0.2.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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 show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@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)
You can disable automated security fix PRs for this repo from the
[Security Alerts page](https://github.com/dora-rs/dora/network/alerts).

</details>

Bumps [array-init-cursor](https://github.com/planus-org/planus) from 0.2.0 to 0.2.1.
- [Release notes](https://github.com/planus-org/planus/releases)
- [Changelog](https://github.com/planus-org/planus/blob/main/CHANGELOG.md)
- [Commits](https://github.com/planus-org/planus/compare/v0.2.0...array-init-cursor-v0.2.1)

---
updated-dependencies:
- dependency-name: array-init-cursor
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Add support for mask within `dora-rerun` to be able to debug 2d masks in
3d.

Minor Magma fix

minor fix to node-hub documentation to reflect directory structure of
pre-built nodes. Additionally adding ruff lint rules to example
pyproject.toml that were introduced in #888 . closes #928

P.S I updated `README.mdr` to `README.md` presuming it was a typo, but
it looks like .mdr is an actual file format so idk if that was
intentional :)

Make it possible to retrieve data asynchronously within python asyncio.

This is possible due to `experimental-async` from pyo3.

Note that this feature should be considered experimental as long as pyo3
async is marked as experimental.

This feature required to remove events delayedcleanup as it was no
longer used.

Related to #854. In this, we are using Arrow::FFI module to send and
recieve data from rust. Two functions are defined named as
event_as_arrow_input() and send_arrow_output(). Both send data in form
of
[FFI_ArrowArray](https://arrow.apache.org/rust/arrow/ffi/struct.FFI_ArrowArray.html)
along with its
[FFI_ArrowSchema](https://arrow.apache.org/rust/arrow_schema/ffi/struct.FFI_ArrowSchema.html).
These functions provide interface through cxx. One issue i faced was
that cxx doesn't support sending opaque types in format so had to use
raw pointers for transfer.

DataTypes mentioned
[here](https://arrow.apache.org/docs/format/CDataInterface.html) are
supported to transfer using these functions. Due to my exams i have only
tested with INT32 and String.

I have added a Simple example using these functions in
dora/examples/C++-DATAFLOW2. Currently i am supposing arrow is installed
on user system while running above command as build command looks for
arrow in user pc. This approach can be changed with downloading package
at build and placing it locally in folder for use. We can run example
using `cargo run --example cxx-dataflow2 `

Previous api was left unchanged and still works the same. I tested using
previous examples.

Fix CI indentation

So, As mentioned
[here](https://github.com/dora-rs/dora/pull/913#issuecomment-2747339237).
I did these changes and tried it with "Hennzau" fork and it seems to be
working fine.
```Checking for updates...
Checking target-arch... x86_64-unknown-linux-gnu
Checking current version... v0.3.10
Checking latest released version... v0.3.11
New release found! v0.3.10 --> v0.3.11
New release is compatible

dora release status:
  * Current exe: "/home/arlott/gsoc/dora/dora/target/debug/dora"
  * New exe release: "dora-cli-x86_64-unknown-linux-gnu.tar.gz"
  * New exe download url: "https://api.github.com/repos/Hennzau/dora/releases/assets/240150528"

The new release will be downloaded/extracted and the existing binary will be replaced.
Do you want to continue? [Y/n] Y
Downloading...
[00:00:03] [========================================] 15.41MB/15.41MB (0s) Done
Extracting archive... Done
Replacing binary file... Done
Successfully updated Dora CLI to version: 0.3.11```

Instead of transformers code

[`cargo-dist`](https://github.com/axodotdev/cargo-dist) is used by
several big projects (including `uv`). It's really powerful, and so I
think it can be useful to use it.

# Changes

The old `release.yml` was doing both `crates.io` releases and the
build/upload of the `dora-cli`. Because `cargo-dist` needs its file to
be `release.yml`, I renamed the old one `cargo-release.yml` (just as
`pip-release.yml`).

Also the `cargo-release.yml` is just doing the release in `crates.io`.
The build/upload is now the role of the new `release.yml` file with
`cargo-dist`.

# Scripts

```bash
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/dora-rs/dora/releases/latest/download/dora-cli-installer.sh | sh
```

```bash
powershell -ExecutionPolicy ByPass -c "irm https://github.com/dora-rs/dorareleases/latest/download/dora-cli-installer.ps1 | iex"
```

Advantages => support all platforms, and also all shells

# Usage

Whenever you create a Release and the associated tag with it, it will
launch the workflow and when artifacts are ready, they be added to the
Release announce. **The version of the tag created must match the crate
version in the Cargo.toml file**

This pull request introduces the `gamepad` and `dora-mujoco-husky`
nodes, a MuJoCo-based simulation of the Clearpath Husky robot for the
Dora framework. The changes include adding the necessary files for the
node, setting up the simulation environment, and providing documentation
for installation and usage.

Key changes include:

### Documentation:
* Added `README.md` with detailed instructions on features,
installation, running the demo, usage, and development.

### Configuration:
* Added `demo.yml` configuration file to define the nodes and their
connections for the simulation demo.

### Code Implementation:
* Implemented the main simulation logic in `dora_mujoco_husky/main.py`
to handle velocity commands and provide position/velocity feedback.
* Added a gamepad node that uses pygame to get controller input and
outputs the cmd_vel

### Simulation Model:
* Added `husky.xml` to define the MuJoCo model of the Husky robot,
including its physical properties and actuators.
* Added the required mesh files for the Husky robot.


This PR addresses #905