Do you want the autopilot to keep driving after a crash is detected? Turn off right before a crash is the only surefire way to make sure the fscking engine turns off before the crash which could cause control signals to get fubar and not disengage.
notfromhere
joined 2 years ago
What is that virtual pipe organ and why is it using 69 GB RAM when running?
I have a small cluster of Pis running k3s kubernetes and running several services for my household. Yea they could all run on a single beefy server but I had fun learning it all.
I have one of those, it’s a small adapter, and it adds ground loop noises / buzzing when charging… probably because they are made cheaply without proper isolation from the switching power supply.
They used to make docks for iPods that would do both, I would look for that style.
Pi 3B has dedicated bus for SD card but ethernet and usb share bandwidth. Enable zram, disable all swap and keep using sd card.
It sounds like someone out of their jurisdiction should host the repos and tell them to pound sand.
How is the plugin illegal?
Are all services running on the same machine? You mentioned same network… you also said you added your “docker instance” to tailscale. I think some clarifications on what those two things mean could help narrow down the problem.
E.g. do you have multiple physical machines running docker containers? Each one you want to access needs to be added to tailscale, OR, set up a tailscale gateway?
It’s a system that has full blame on the driver to beginwith so what exactly are you trying to say? Driver has blame the whole time. In the fraction of a second before impact, the automated system turns off as a safety precaution to reduce the impact as much as possible.