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…
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.
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.
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.
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?
Interesting, GPG has been working just fine for me so far.
My main issue with it remains that barely anyone else uses GPG.
As long as people are using Rust, it will necessarily attract this kind of action. This won’t be the last attack we will see.
I think the team has handled it quite well.
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.
There are even little interactive tools for it like: cargo-wizard
Good move. Especially for incremental builds linking tends to take up quite a large percentage of the compile time.
I’ve mostly switched to mold for that reason but having a fast default linker is nice.
How well NixOS fits your purpose really depends on what you want to do with the OS. If you’re just going run a bunch of docker containers, you could manage them via Nix but its a little cumbersome.
Where NixOS really shines for small servers are the so called NixOS Options.
They allow you to install tons of services on bare metal but manage all the configuration for you. E.g. open the correct firewalls ports, run a dedicated DB or cache, etc. and all those simply require you to enable them with an = true;.
Smaller projects might not have a NixOS Option available and some options are more and/or easier configurable than others, but if you’re running just a few common services you could feasibly manage your whole server with just one native config file and no docker shenanigans.
I’d recommend checking what’s available under the link above. If you wanna go the container route instead, you have the option of just using docker non-declaratively as on every other distro (but then you lose some of the benefits NixOS gives you), or you can declaratively have NixOS manage all the docker containers. There are a few ways to do and manage this so some further research will be required.
Then helmfile might be worth checking out
You dont need to manually handle the WG config files. This isn’t really an issue when it’s just you and your two devices, but once you start supporting more people, like non-technical family members, this gets really annoying really quickly.
Tailscale (and headscale) just require you to log in, which even those family members can manage and then does the rest for you. They also support SSO in which case you wouldn’t even have to create new accounts.
There are some experimental models made specifically for use with Home Assistant, for example home-llm.
Even though they are tiny 1-3B I’ve found them to work much better than even 14B general purpose models. Obviously they suck for general purpose questions just by their size alone.
That being said they’re still LLMs. I like to keep the “prefer handling commands locally” option turned on and only use the LLM as a fallback.
To expand: Just configure whatever profile you’re using (dev, release, …) to have link time optimization (lto) enabled:
[profile.release]
lto = "fat"
I’ve had this exact same gripe and can thankfully report that running EarlyOOM has fixed this for me.
And please don’t understand this the wrong way.
Ibis seems like a really cool project but with it being roughly half a year old me and many other people here simply have never heard of it before.
Including even a single short sentence describing what Ibis is in this and future posts helps us find projects that we care about more easily.
And we obviously care about Rust projects, otherwise none of us would be here.
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.