-
## Introduction
Currently the `Message` trait is defined like this
```rust
pub trait Message
where
Self: Sized,
{
fn message_id(&self) -> u32;
fn message_name(&self) -> &'stati…
-
It would be nice to have a way of non-blocking `recv()`. I think there is many applications for it, just like in [`std::sync::mpsc::Receiver`](https://doc.rust-lang.org/std/sync/mpsc/struct.Receiver.h…
-
Hello, so I was building a simple GCS. A simple UI on the front and a python server at the back.
Using websocket to handle commands and Server-Sent Events (SSE) for unidirectional information (tele…
-
I'm trying to send a message with a oneof inside of it:
```proto
// [RINF:RUST-SIGNAL]
message VehicleStateUpdate {
oneof updated {
bool arm = 1;
VehicleMode mode = 2;
double batt…
-
### Current behaviour
I am interested in running Blue OS in an x86_64 VM to simulate fleets of systems. I am trying to run the ./install.sh script, but it returns
```
./install.sh
Invalid archi…
-
The verbose mode with mavlink messages is pretty crazy, it would help if we could add an option with the verbose that we could filter the selected mavlink messages with a regex for names.
-
I noticed that the `tokio-1` feature depends on `tokio^1.0` which potentially violates the MSRV check since the latest `tokio` 1.39 requires Rust 1.70. This was likely not caught since the test does n…
pv42 updated
2 months ago
-
Sorry I can't be more helpful. Rust is outside my current expertise
### Building steps
- Followed steps to build in README.md
- checked out release T3.12.1
- Received error
- Re-ran with RU…
-
With #255 support for `tokio`-based `async` was merged, adding `async` versions of `write_versioned_msg` and `read_v2_msg` which is very welcome (as it is something I was thinking of doing myself).
…
pv42 updated
2 months ago
-
The feature `emit-extensions` that is supposed to enable mavlink v2 extension does not currently work for versions 0.13.x.
This can be seen when comaparing the documentation (which enables all featu…
pv42 updated
2 months ago