this post was submitted on 19 Nov 2025
358 points (98.4% liked)

Technology

76918 readers
3409 users here now

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

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
358
Cloudfare outage post mortem (blog.cloudflare.com)
submitted 1 day ago by homura1650@lemmy.world to c/technology@lemmy.world
57 comments fedilink hide all child comments
 

The issue was not caused, directly or indirectly, by a cyber attack or malicious activity of any kind. Instead, it was triggered by a change to one of our database systems' permissions which caused the database to output multiple entries into a “feature file” used by our Bot Management system. That feature file, in turn, doubled in size. The larger-than-expected feature file was then propagated to all the machines that make up our network.

The software running on these machines to route traffic across our network reads this feature file to keep our Bot Management system up to date with ever changing threats. The software had a limit on the size of the feature file that was below its doubled size. That caused the software to fail.

you are viewing a single comment's thread
view the rest of the comments
[–] ranzispa@mander.xyz 7 points 1 day ago (1 children)

Before today, ClickHouse users would only see the tables in the default database when querying table metadata from ClickHouse system tables such as system.tables or system.columns.

Since users already have implicit access to underlying tables in r0, we made a change at 11:05 to make this access explicit, so that users can see the metadata of these tables as well.

I'm no expert, but this feels like something you'd need to ponder very carefully before deploying. You're basically changing the result of all queries to your db. I'm not working in there, but I'm sure in plenty places if the codebase there's a bunch of query this and pick column 5 from the result.

[–] felbane@lemmy.world 2 points 1 day ago

"Claude said it was fine, ship it."