My only gripe with btrfs is that I’ve had systems come down from a single drive failure in raid quite “often” when compared to other FS.
ZFS is a ram hog but I always could do a live resilvering without downtime.
My only gripe with btrfs is that I’ve had systems come down from a single drive failure in raid quite “often” when compared to other FS.
ZFS is a ram hog but I always could do a live resilvering without downtime.
Probably, still remains that out of all the bots I’ve seen this is the only one with format issues. I believe a minimalist approach to be preferable for bots since their goal is spreading information over a large userbase with various client, from CLI to native web page.
“Oh, this new post already has a comment, let’s check it out! … Dang it!”
After the third or fourth time it’s just spammy, and the bot formatting just doesn’t work on connect.
Any evidence of that? Genuinely curious as I can’t really find anything about them being by the same people and forgefed started as mailed-based prior to forgejo existing.
edit: seems like they are funded by different organizations and the main contributors to forgefed never worked on forgejo, they worked on vervis though.
Just to give credit where credit is due, git federation is a Forgefed Initiative
Forgejo is implementing it in their platform.
Sorry that’s all I could think about
One of the first interaction I witnessed from the forgejo guys was this PR:
https://github.com/go-gitea/gitea/pull/27455/
The interaction and stubbornness of earl-warren felt like it was just that, provoked drama.
I use owncloud infinite scale and overall its rock solid. The downside is the lack of plugins. Nextcloud has been nothing but trouble for me and every update was a mess so I decided to try OCIS and for my need I was extremely satisfied.
Now, I admit, I’m not one to get carried by the drama in the FOSS sphere (still use Gitea) but I do agree there is an history to the separation of owncloud and nextcloud that can make some people uncomfortable. Having a choice is good I believe.
tar -h
Edit: wtf… It’s actually tar -?
. I’m so disappointed
There you go:
# Start an infinite loop because True will always be True
while True:
# try to run the main function, usually where everything happens
try:
main()
# in the case an exception is raised in the main function simply discard (pass) and restart the loop
except:
pass
For those curious about the drama & lack of wide adoption surrounding the walrus operator
https://dev.to/renegadecoder94/the-controversy-behind-the-walrus-operator-in-python-4k4e
It’s a shame because it’s a really nice feature.
I started using hatch lately and really like how I can manage everything from the pyproject.toml file
My secret to high uptime:
while True:
try:
main()
except:
pass
deleted by creator
Edit: something that are not arm based
You want pre-built to run ollama, that’s at least gonna cost you an arm, maybe even a leg.
I use those on server hardware that don’t have onboard graphics from which I need more than simple CLI. Also useful if you have an HDMI KVM and only VGA output.
The infrastructure is growing quite fast considering how young the whole EV market is.
As for the price that’s exactly what blanket incentives would do. Affordable EVs are hardly developed currently because people buy larger more expensive (profitable) vehicules that would normally be 10k+ over their budget and that 10k is free money in the pockets of the manufacturers. Start giving incentives only for affordable EVs and they will start appearing all over the place
Incentives are great for a few years but then they just become part of the price. Most provinces will eventually remove their incentives towards EV as they become mainstream or at least transition to a subset of EVs maybe leaving out those considered luxury.
What they shouldn’t stop investing in is the infrastructure making those EVs a reliable alternative.
It is true for raid 5 & 6. Raid 0, 1, and 10 are supposed to be production ready. I use raid 10 only with btrfs, anything else and I use zfs or mdadm.