Brian Schwind

I remember adding a patch for this a long time ago, before the actor crate got split out into its own repo. I'm actually not sure why it never got...

One thing I had experimented with in the past was storing actor addresses in a "registry" upfront, and then actors could request an address of a certain actor type via...

One crate we were eyeing is [metrics](https://crates.io/crates/metrics), which is a metrics facade similar to `log`. In general I _would_ like to remove the generic bound on `MetricsHandler` since it complicates...

The transistor leakage current theory sounds pretty likely! The weird thing is, I was able to remotely update one of the panels remotely in our staging environment, so it's at...

@noyez if we get the merge conflict resolved and apply @mcginty 's suggestion, we can get this merged and release the next version of innernet :)

> next release? ... let's get this merged then. I'm looking forward to the new release! thanks! Yep next release. It seems the merge conflict is still there though so...

For the conflicting line, I think you just want it to be this: ```rust let mut command = Command::new(get_userspace_implementation()?); ```

Ah, it seems I can resolve the merge conflict myself, didn't know I could push to branches on forks.

Hi @stheid , you'll likely need a newer version of cargo/rustc than what's currently installed on that raspberry pi. I _think_ you need Rust 1.56 or later.

I've successfully built innernet on a Pi 4 (faster/better hardware, I know) by increasing the swap. The default swap settings resulted in a failed build. I followed steps [here](https://nebl.io/neblio-university/enabling-increasing-raspberry-pi-swap/) to...