I ran into the same issue not so long ago and at least for no_std I had to resort to using the async_trait crate. (The project is no_std but has alloc)
I can’t recall the exact error so it might have been due to mixing async and non-async methods in the same trait. I would have to look at it again…
Absolutely. Maybe a poor choice of words on my part. My intention was to state that this is not a thing you simply hang out in the wind and leave, but instead a vehicle that needs to be controlled to stay within its operational envelope.
I can imagine problems like tethers or lines getting crossed when the vehicle makes fast turns due to wind shear or frequent direction changes. You probably can’t operate it in those conditions.
You would think so but even normal ground-fastened wind turbines shut off when winds get too strong.
This being somewhat of an aircraft I absolutely expect them having to land it before storms roll in.
If you land it facing up- or downwards and deflate the balloon segments it would probably be fairly flat and compact for storage.
Source (German)
Would it have cost you so much to leave a link at the bottom of the post?
I have never used them but there are some tools that advertise being able to run GitHub Actions locally, like WRKFLW.
Indeed
Also the normal and rpi versions are two completely independent implementations of the same software. So now the LLMs have twice the maintenance load.
I didn’t diff the two files but even the startup and control code appears to be custom for each version.
Its a fully electric drivetrain with a gas generator. When the battery runs low you can recharge it (even while driving) using the generator.
So you don’t have the complexity of a combined hybrid drivetrain, but instead a normal BEV one plus a power generator, both of which are very well understood problems.
Another benefit is that the generator can always run at its most efficient rpm/power point and is decoupled from the speed of the wheels.
Interestingly Wankel engines have been making a bit of a comeback for this purpose since they can be built more compactly for the same output power.
A drawback compared to hybrid drivetrains is that both components need to be built for “full” load, whilst a hybrid drivetrain can combine powers to reach maximum performance, meaning each of the motors only has to carry half (or part) of the total load.
Since projects of the same language often use the same tooling this makes it easier to clean up the whole directory by running something like this:
for d in ./*/ ; do (cd "$d" && somecommand); done
somecommand could be cargo clean if you’re in the Rust directory for example.
Just out of curiosity I don’t see how 4 sticks die together at the exact same time unless the PSU is/has fucked up hard.
I’d argue that the likelihood of 4 sticks failing together is much lower than the MOBO or CPU or PSU failing in a way that makes RAM inaccessible.
Typically you’d see one stick failing at which point you could take it out and run with the other 3 (or 2 depending on configuration).
Anyway if you ever intend to return its probably best to keep the rest of the components because who knows which of those will be up next for a shortage/crisis.
Depends on the exact system but there will be a method to switch to a newer release channel without reinstalling. Rinse and repeat every x years.
I assume you mean AVIF? Because AV1 is not an image (file) format but a video compression format (that needs to be wrapped in container file formats to be storable).
The std::offload project is kinda cool. Hadn’t heard about that before.
It’ll be interesting to see where that leads.
I was under the impression that the compiler already optimizes out a lot of clones where the clone is primarily used to satisfy the borrow checker. Is that not the case?
Like you already hinted at batteries are DC systems and can only be charged using DC. Many EVs have at least a small AC to DC converter on board. When you plug it into an AC source the charging speed is limited by the size of that converter.
DC charging stations bring their own converters which are oftentimes much more powerful and therefore heavier than what your car carries along.
Whether you use an external 19kW converter or your cars internal converter doesn’t make a difference. In both cases the cars charging circuitry will monitor for dangerous situations such as overheating and throttle the charger down if need be.
The important question is how large your cars converter actually is. Sure the L2 charger provides 19kW AC but can your car’s converter actually use all of that?
If it can only do 10-15-ish kW then it’ll charge slower and therefore won’t tax the battery as much as a DC charger with 19kW would.
I don’t know what car this is and how PHEVs play into this but existing BEVs have been charging with much higher speeds for more than 100,000 miles and generally don’t end up with broken batteries.
Depends a lot on the make and model of course, as I’m sure there are some horrible examples out there. But the public fast chargers wouldn’t be under such demand if it was that damaging to the cars.
The post text doesn’t seem to get displayed on some clients (Voyager) so I’ll attach it here as well:
asciinema (aka asciinema CLI or asciinema recorder) is a command-line tool for recording and live streaming terminal sessions.
This is a complete rewrite of asciinema in Rust, upgrading the recording file format, introducing terminal live streaming, and bringing numerous improvements across the board.
Not just on the web. I’ve previously used it to embed a short clip in a presentation.
The nice thing is that it doesn’t do a massive screencap but only captures the text. This way the replay will be freshly rendered at native resolution.
Stuffing batteries into the cardan tunnel was a stupid idea. If you want your EV to have any range you need to design the chassis from the ground up for that purpose. You know just like they did for the Golf with an ICE engine.
I’m not against a refreshed EV Golf but that earlier concept wasn’t the best implementation.
There are even little interactive tools for it like: cargo-wizard
Same here. Literally just set it up and now this.
I hope the author will roll this back or someone else makes a fork. I don’t want to immediately switch technology to XMPP/Matrix/… and have to do it all over again.