Technology

60078 readers

4458 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

Flaw in Git bloated Microsoft repository by a factor of 35. (www.techzine.eu)

submitted 1 month ago by [email protected] to c/technology

7 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] breadsmasher 11 points 1 month ago (1 children)

The culprit: name-hash collisions. With files like changelog.md and changelog.json, Git found all kinds of differences with each commit even though there often were none, which gradually added 173GB of unnecessary bloat. However, the changelogs were in completely different packages. The algorithm checked only the last 16 characters of the path, so package differences were not considered.

[–] [email protected] 11 points 1 month ago

thanks for the reply, but i think i got that. from the linked article:

For example, if you changed repo/packages/foo/CHANGELOG.json, when git was getting ready to do the push, it was generating a diff against repo/packages/bar/CHANGELOG.json! This meant we were in many occasions just pushing the entire file again and again, which could be 10s of MBs per file in some cases, and you can imagine in a repo our size, how that would be a problem.

but wouldn't these erroneous diffs not show up in git diff? it seems that they were pushing (maybe automatically?)without inspecting the diffs first