Interesting, I did not expect them to meet SIL4 standards, that’s not an easy achievement.
Interesting, I did not expect them to meet SIL4 standards, that’s not an easy achievement.
Sounds a lot like flattening with extra steps to me
It should also be noted that the post will only appear on that kbin instance, and no other instances.
I recently had GCC give me the error “returning to the gate for a mechanical issue”, fun stuff as well
I’m not sure I’d classify it as a bug. Instances can temporarily go down at any moment for numerous reasons, to account for this instances will keep retrying to connect with an exponential backoff. At what point should an instance assume that another instance is permanently gone?
Perhaps a good start would be adding a status indicator to every community with something like last sync: 1 minute ago.
You can see that an instance/community is gone by visiting the instance directly. In this case at https://lemmy.fmhy.ml/c/imaginarymechas (which obviously won’t work now, as it’s gone).
Whenever you submit a post to a community, first your own instance saves the post locally, then sends it to the instance hosting the community, this instance then sends it to any other instance with users subscribed to the community. When the hosting instance is down, then that step of course fails, resulting in the post being only visible to members of your own instance.
Depends on what undefined
we’re talking about. JavaScript undefined is just a value for undefined variables.
In C undefined behavior could be anything, ranging from reading in random garbage to time travel or summoning eldritch terrors.
This is just an educated guess, but could it possibly mean that it couldn’t create your post?
That’s not entirely true. OverlayFS supports page cache sharing for files in image layers. If your images share the same base image layer, then it should share libc and friends in the page cache.
https://docs.docker.com/storage/storagedriver/overlayfs-driver/#overlayfs-and-docker-performance
Does the People(Vec) even work if you don’t specify the type inside the Vec?
Sweet! Now I don’t have to recursively write comments to explain the meaning of each comment
Can’t you just use the get_or_init
method instead of get
inside the push_log
method? This would initialize the cell on first use. You’d still need a Mutex inside of it to acquire a mutable reference to the vector.
To add on to this, if you’re using some random RAM stick picked out of the gutter, then it might be worth it to run memtest86+. Bad RAM sectors can give some weird unpredictable issues.
I don’t think oli-obk has any say in this as they stated the following:
Because this crate is owned by dtolnay and he may do with it as he wishes. My personal opinions on the topic are irrelevant.
If it creates infinite number of people, it could solve world hunger with some good ol’ Soylent green thinking. Although you might want to figure out how to slow down the trolley at some point.
What’s weird about the C++ one? At least that one is the same in a bunch of languages
They sold a physical switch hacking device
Did you try requesting your data? I got my data within a day. They probably mention 30 days because that’s the legally defined deadline, and to give themselves some leeway in case the automated system has issues with some user.
It also makes sense for them to make it a low-priority task, as they have a really long deadline for it, and you don’t want it affecting the main site.
It has some good parts, such as the ability to use for loops, and the fact you can kind of avoid using it as much thanks to it’s webassembly support