Gentoo also has a tracker [1] for GCC 15 issues that they've been working on as well. (Note: GCC 15 is masked in Gentoo so you have to go out of your way to install it)
He does not want your code anyway, sqlite is public domain. this has several implications. One of which is the author wants nothing from you. Note that public domain is fundamentally different than the usual method of releasing code, which is to issue a license to distribute a copyright protected work. Putting a thing into the public domain is to renounce any ownership over the thing.
I think that the proper spirit of the thing is that if you have patches to sqlite is to just maintain them yourself. if you are especially benevolent you will put the patches in the public domain as well. and if they are any good perhaps the original author will want them.
In fact the public domain is so weird, some countries have no legal understanding of it. originally the concept was just the stance of the US federal government that because the works of the government were for the people, these works were not protected by copyright, and could be thought of as collectively owned by the people, or in the public domain. Some countries don't recognize this. everything has to be owned by someone. and sqlite was legally unable to be distributed in these countries, it would default to copyright with no license.
Intel has always had randomly supported ECC on desktop CPUs. Sometimes it was just a few low end SKUs, sometimes higher end SKUs. 14th gen it appears i9s and i7s do, didn't check i5s, but i3s did not.
All of these sort of things are just based on hours used. It's like looking at your hot water heater warranty and replacing it when it's over (I live an an area where the PPM of the water is rather high and hot water heater warranties are basically calibrated for water like mine, so we do have to replace them on warranty expiration, most places you at least get a few years or double)
Changing a hot water prematurely is probable less expensive than having one blow the bottom out and flood whatever area it is in. I don't have a basement, so my central unit and water heater share a utility closet in the hallway sharing a wall with a bedroom. It's a pretty bad design flaw, as during the summer of 110°+ temps, it is unnecessarily heating the house. IR temp shows that shared wall from the bedroom side over 90° radiating into that bedroom. </rant>
Maybe, but it's a rental, so only some much to be done about that. So much was defined by me as buying a $30 roll of insulating whatever it is that then got stapled to the interior wall of the closet. Took the thermal temp down 15° on the bedroom side of the wall.
I've found at times that starting with isopropyl alcohol doesn't get enough of the oxidation off for it to keep working normally more than a day or two, while the fiberglass pen being used once feels like a more permanent fix. (Maybe after 10 years it will have issues again, but it at least for sure keeps working for weeks or months). I had an issue of this sort really bad with a GBA power switch. You can try to get a little alcohol in from the outside and move it back and forth and maybe it seems to work for 1-3 days, but then it would be intermittent again. The proper fix was to desolder the shielding on the power switch to get inside, and then clean off the oxidation from the contacts inside.
I should've also mentioned this in my first comment, but I recommend opening up the cartridges before cleaning them. I don't think you can get at the whole contact properly while the shell is on, and it's easier to do an even up and down motion along the each contact when the shell is out of the way. I go back and forth for a couple seconds on each one until it looks shiny. As a bonus you can possibly find out if your game is genuine or counterfeit while it's open and the chips are visible.
You can also put the 72 pin connector in boiling water for like 30 mins, take it out and let it cool. That should reset the pins back to "factory condition"
I think it all comes back to people being upset about the Ubuntu PulseAudio switch. Ubuntu did a bad job when they switched to PulseAudio and caused lots of issues. Lennart Poettering was lead dev for both projects and it's weird how much the anti-systemd crowd get their panties in a bunch over him and also PA.
> He also fucked up some in systemd, journalctl being biggest example.
"Let's just invent our own non-ACID file format instead using what's already available." (Like perhaps SQLite.) Howard Chu of OpenLDAP had a rant on this:
Does journald support off-host log shipping yet? Because for all its supposed replacing of syslog, as a sysadmin I still have to run (r)syslogd to send things to a central log host via RFC 3164/5424 anyway.
I'm pretty sure it's just him wanting to toy with databases and picking systemd to be his victim.
I'd expect when he finds new toy to keep himself busy someone else will fix it to actually work properly for the most time like it happened with PulseAudio
Most of the c string usage appears to be just for libobs, which is a C library. They have a few constants that are perfectly fine and the rest of their string usage is actually std::string ...
