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.
-
@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
-
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
What could possibly go wrong? -
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.
-
@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.
@chris @distractal @sinbad @JeremiahFieldhaven curious how close to addiction itll feel like at 10x the cost
and my dude outside of $ loss if your gaming like an addict its an addiction
-
@mirabilos @mavu @cap_ybarra @JeremiahFieldhaven There is also github.com/gokrazy/rsync which i haven't tested yet.
@billchenchina
https://codeberg.org/small-hack/open-slopware#file-transferring lists the following rsync alternative as LLM free: https://github.com/kristapsdz/openrsync
@mirabilos @mavu @cap_ybarra @JeremiahFieldhaven -
@chris @sinbad @JeremiahFieldhaven Here's my question... is it really, solving the problem for you? Like, actually? Given all of the costs in the full context of how it operates?
I don't believe that it is.
Can you trust everything it outputs? Are you able to catch any problems with it 100% of the time? Are you somehow able to avoid it anchoring your thinking around a particular method?
Let's assume it does solve the problem, and that somehow a purely ethical AI is produced that magically solves the labor, environment, plagiarism issues, and that is correct 100% of the time.
Even if it does, you are slowly eroding your ability to solve problems of that nature independent of the agent.
No matter how careful you are, no matter how smart, how skilled, how well-versed.
You cannot beat cognitive surrender.
@distractal @chris @sinbad @JeremiahFieldhaven
I am sharing a critical view regarding 'cognitive surrender', yet a reality check on expectations:"... a purely ethical AI is produced that magically solves the labor, environment, plagiarism issues, and that is correct 100% of the time."
=> does code written by humans fulfill all these criteria, I mean even approximately?
-
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 That really sucks. I pretty much just install whatever updates #Debian sends me, might have to start watching that much more closely. #rsync
-
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 ...and fork and fork and fork and fork... At work I just don't build recent versions anymore. Which is fine because we just use it for LAN installs anyway. But yes, all this stuff needs forking, sadly. Once the current maintainers of important projects leave reality for good, that seems like the only way forward.
-
@chris @distractal @sinbad @JeremiahFieldhaven curious how close to addiction itll feel like at 10x the cost
and my dude outside of $ loss if your gaming like an addict its an addiction
I'd chime in here and say that good people suffer from substance abuse. Living in Las Vegas and watching the penny pinchers succumb to a big payout from a slot machine was both fascinating and very sad. AI gives a programmer the illusion that they are now the power code maker they always envisioned themselves to be. That isn't much different than cocaine. We're losing good people to this.
-
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 programmer's introduction to AI: https://www.goodreads.com/book/show/191113.Don_t_Let_the_Pigeon_Drive_the_Bus_
-
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 Some of these commits are repairing defective generated code with other generated code.....
🫣 -
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.
Oh fuck not rsync too?
I've been using it for I-don't-even-know how long, probably close to 3 decades. -
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 the amount of crap that’s broken after 3.4.1 is just wow
https://github.com/RsyncProject/rsync/issues -
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 i had to review/rewrite some AI written code the other day. (That i was handed)
The problem it was solving was a well known one, and it was only solving the smallest subset of it.
The code could compile and run, but:
- because i have some domain knowledge i could see that the output was not correct
- it's sync feature was not satisfactory, at all
- the code was some of the worst I have seen in a long, long time things were split in ways that made absolutely no sense -
@JeremiahFieldhaven i had to review/rewrite some AI written code the other day. (That i was handed)
The problem it was solving was a well known one, and it was only solving the smallest subset of it.
The code could compile and run, but:
- because i have some domain knowledge i could see that the output was not correct
- it's sync feature was not satisfactory, at all
- the code was some of the worst I have seen in a long, long time things were split in ways that made absolutely no sense@JeremiahFieldhaven I don't understand how anyone trusts the output of these things.
Yes, you can ask for small examples of things, of you are too lazy to open man pages, etc.
But putting any trust in the code these things spew out without thoroughly reading and understanding every line is incomprehensible to me. And when i do this, i tend to find I'd have been much better off just sitting it myself.
-
@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 Learning is forever but a Claude Code subscription bills monthly.
-
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 I feel like being lazy to actually go through updates often on my arch install has been paying off lately
