Simonas

@mycoliza Since you’re using NixOS, you might be able to just build a 2 systems that can mount the new/old pool by name using: fileSystems."/" = { device = "tank/root"; # vary this fsType = "zfs"; }; # and so forth for all mountpoints

@mycoliza And if things fail to boot for verification, you can reboot with the sata module blacklisted? Or just boot into a recovery and trim the SATA disks before trying again.

TIL you can’t rename a zpool without unmounting it. welp, guess i’ll be adding SATA drives to “nvme-pool,” then…

@euroremontas Nuolaidines bulvytes iki 30mm.

@Akamai writes the ak_bmsc cookie without asking (EU), and then blocks (with 403 Forbidden) any requests containing that cookie. ROFL?!

@mycoliza @ManishEarth @lunasorcery Eh, seems more like an issue with how rustfmt formats stuff. To be fair, I do agree that keeping track of "is this still a function call?" can be difficult if you encounter them after a longer closure (or two!), and it’d remain an issue regardless of formatting.

@ManishEarth @lunasorcery .do_stuff(foo, bar, |x| { blah(x); wiggle(x) }) looks better than .do_stuff( |x| { blah(x); wiggle(x) }, foo, bar, ) (at least, IMO)

@lunasorcery not sure but I assume because rust was partly designed by rubyists and ruby loves closure-at-the-end bc it has special syntax for it

@nick_r_cameron For the latter question, not so much. The `Rust` ABI isn't particularly awesome, but with `Rust` ABI being unstable there’s still hope that using it over any other ABI might produce more efficient code in the future.

Is there ever a reason to have an extern item which is not no_mangle or a no_mangle item which is not extern?

@nick_r_cameron `no_mangle` causes symbol collisions when crates get duplicated. If there's an option to avoid using `no_mangle` it is always beneficial to do so. Passing callbacks, calling functions from inline assembly, and similar uses don’t need it for example.

The 2022 State of Rust Survey is here! surveyhero.com/c/sfhmgxgd

@Android Though to be fair, my take on internet connected vehicles is “they were so preoccupied with whether they could, they didn’t stop to consider whether they should”.

So, uh… Does @Android Automotive mean that 5 y.o. vehicles with it will be running all of them unpatched RCE exploits? I’m not really finding any support timelines from integrators yet, which suggests “yer on yer own m8” to me.

I’m sure this is all just y'all at Google becoming better at C and C++ now that you all that extra time during the lockdowns to get good!

Any DDoS reliant on distributed nature would mostly just hit those secondary servers. Yeah, you’ll lose traffic in the secondary markets, but… in the primary market your servers would have a much easier time handling the extra load that could only be characterized as a “meh.”

Idea: could anycast be used by regional websites as a DoS/DDoS mitigation mechanism? Basically spin up a fraction of servers outside of your primary markets and shovel all your traffic in secondary markets to those servers.

I’m told Mr. Henry of induction fame is the reason and cause of us not getting hellabytes.

@irevoire @jntrnr @rustlang Did you know you can catch that other issue and have the program continue the execution anyway? Might just work for you too.

@jntrnr @rustlang I box::leak everything, and then later, when you don't need the reference anymore, you can do a simple call to drop(from_raw(...)) I never had any borrow checker issues with this coding pattern (let's not talk about the other issue I had thought)

I’m positively sure it is going to be something incredibly mundane, and yet an art piece worthy of the most posh museums out there.

I can’t wait to see what the very last tweet will be before the whale takes off on its very last trip.

@whitequark Not to mention that a hob really rarely stay at peak rated power for extended time. The battery would really start mattering a lot when there are 2+ pans at high heat. And unless there's a cooking technique that involves making charcoal, pans rarely stay on high for long.

I would hold off on stating how quickly that thing requires repair or becomes e-waste; you do have enough space there for Li batteries storing enough energy for twenty minutes at reasonable power, so if they cycle them very gently, it could last a while twitter.com/polyparadigm/s…

can someone who's from the US clarify how this product makes sense. like, if you want an electric stove and you go through the trouble of getting a countertop integrated one, why don't you have or get 208 V there? why do you need batteries in your stove? twitter.com/sdamico/status…