So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven oh damn it all
running screaming into the woods never to be seen again is sounding more and more like a reasonable career path
-
@cap_ybarra @JeremiahFieldhaven on rsync, this is scary. It's getting to a point where just stopping updates for a while on crucial systems seems safer than applying them.
@mavu @cap_ybarra @JeremiahFieldhaven basically, we already stopped upgrading to newer versions where ensloppification happens, but it’s now being backported under the guise of security fixes, ill though-out ones (or not-at-all in the case of slop). This is a problem.
rsyncis so critical, I wonder if there are people versed enough in it who could hard-fork the last workable pre-slop version and maintain it from there. No need for big fancy new features, just keep it working and safe and secure. (openrsyncseems to be both incomplete and unportable at this point.) -
@mavu @cap_ybarra @JeremiahFieldhaven 3.4.3 looks like mostly security changes (couple bugs say security fixes broke their thing, so it might be the case for your problem). If you only ever rsync with trusted machines, you're all good, but more broadly sitting out future security fixes is less appealing than sitting out future features
@rf @mavu @cap_ybarra @JeremiahFieldhaven not if they come with regressions
then you’d rather mitigate instead of applying the broken patches. -
@distractal @sinbad @JeremiahFieldhaven I'm fighting cognitive surrender every day. Either I get tasks done quickly, or I just give up and don't do anything at all. I mean, I could just go back to wallowing in self destructive ideation for hours on end.
@chris @distractal @sinbad @JeremiahFieldhaven i dont think you know what those words mean
and if your solveing depression with AI well thats depressing and sounds like how people talk about alcohol
-
@JeremiahFieldhaven
Oh damn it all. Tridge has fallen@mav
@JeremiahFieldhaven
Been a while since LLM/AI was shoved into ArduPilot, which is a safety-critical sUAS firmware.I have not taken my stuff out since I saw that land in the project.
Edit:
That was the only context in which I knew of tridge and his storied reputation for making safety-critical code. -
@JeremiahFieldhaven aw, goddamnit!
@spitfire @JeremiahFieldhaven You beat me to it. What is wrong with programmers who should know better?
-
@mavu @cap_ybarra @JeremiahFieldhaven basically, we already stopped upgrading to newer versions where ensloppification happens, but it’s now being backported under the guise of security fixes, ill though-out ones (or not-at-all in the case of slop). This is a problem.
rsyncis so critical, I wonder if there are people versed enough in it who could hard-fork the last workable pre-slop version and maintain it from there. No need for big fancy new features, just keep it working and safe and secure. (openrsyncseems to be both incomplete and unportable at this point.)@mirabilos @mavu @cap_ybarra @JeremiahFieldhaven There is also github.com/gokrazy/rsync which i haven't tested yet.
-
@JeremiahFieldhaven I strongly recommend (if you haven't already) point this out to the rsync maintainers. "Tridge" should have their commit privileges suspended until they can review AI slop.
@ChuckMcManis @JeremiahFieldhaven pretty sure Tridge is the original creator
-
@mavu @cap_ybarra @JeremiahFieldhaven basically, we already stopped upgrading to newer versions where ensloppification happens, but it’s now being backported under the guise of security fixes, ill though-out ones (or not-at-all in the case of slop). This is a problem.
rsyncis so critical, I wonder if there are people versed enough in it who could hard-fork the last workable pre-slop version and maintain it from there. No need for big fancy new features, just keep it working and safe and secure. (openrsyncseems to be both incomplete and unportable at this point.)@mirabilos @mavu @cap_ybarra @JeremiahFieldhaven "versed enough" and "getting versed enough" are both options, IMHO.
It's likely fine to take some time with the next round of updates.
-
@JeremiahFieldhaven fork everything, it's all slop now and needs new caretakers
@JeremiahFieldhaven @cap_ybarra Fork everything and host the forks as far away from GitHub as possible. D:< -
@chris @distractal @sinbad @JeremiahFieldhaven i dont think you know what those words mean
and if your solveing depression with AI well thats depressing and sounds like how people talk about alcohol
@glassresistor @distractal @sinbad @JeremiahFieldhaven I must not know what any of that means, or I wouldn't have said it. You remind me of my brother, who compared my computer use with his gambling addiction. I'm sure those things are the same thing.
-
@glassresistor @distractal @sinbad @JeremiahFieldhaven I must not know what any of that means, or I wouldn't have said it. You remind me of my brother, who compared my computer use with his gambling addiction. I'm sure those things are the same thing.
@glassresistor @distractal @sinbad @JeremiahFieldhaven Is it not cognitive surrender if I want to turn my brain off on a regular basis? This thread is making me want to do that right now. I can do the next best thing and go play video games instead.
-
@glassresistor @distractal @sinbad @JeremiahFieldhaven Is it not cognitive surrender if I want to turn my brain off on a regular basis? This thread is making me want to do that right now. I can do the next best thing and go play video games instead.
@chris @distractal @sinbad @JeremiahFieldhaven could you define cognitive surrender?
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven Even rsync... Software is over
-
@kauer @ChuckMcManis @JeremiahFieldhaven Might have been /s, given «odd humour» in the profile
Also git, indirectly. For those who do not know, look it up.
Tridge is a legend, and our legends are falling to a cognitive virus.
-
@kauer @ChuckMcManis @JeremiahFieldhaven Might have been /s, given «odd humour» in the profile
Also git, indirectly. For those who do not know, look it up.
Tridge is a legend, and our legends are falling to a cognitive virus.
ding, ding, ding. Give this person a donut.
Commit privileges aren't based on bloodline, or history, Etc. When Grandpa tells you the gophers in the back yard are advising him on what to invest his life savings in, you have a gentle conversation with him and move him into a place where he cannot harm himself or others.
We need to hold people updating the code to a standard. You can't get 'fired' in open source, and that's a weakness as folks age out.
-
@distractal @sinbad @JeremiahFieldhaven Though I'm not sure how much the 10-ish % "efficiency gain" is when I can ask an agent to solve a problem for me in 5-15 minutes, or I can spend literally hours poring over a code base to understand what I need to do to fix it myself.
@chris Your understanding of the code base was lacking, so you spent 5-15 minutes making it worse. Is that really the way to go?
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
"This gives more predictable behaviour in case of bugs
where uninitialised or stale memory is accidentally accessed."Gives off I don't want valgrind to tell me I am a bad coder energy.
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven Oh noes
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
every week I go "please, not this", "please not that too"
today it's
please, not rsync
