You could stop it, do a snapshot of the storage and backup that for <1 min of downtime probably.

But at the same time, if you're not a global company, doing it at 3am is probably fine.

Doing a snapshot of the storage while it's running wouldn't be bad either, it'd just be like having cut power at the point of the snapshot, right?

Yes. And the database used by GitLab is Postgres which handles that just fine.

It can be an issue if you are using gitlab as your container/package registry and production workloads need to pull from it, though.

They should be pulling from a pull through scanning repository cache anyway, so they can be scanned before going into production.

I bought ~15 of their cheapest 2.4ghz router to connect payment terminals ~4 years ago and it was a terrible mistake. I thought for a low bandwidth application with the router being decently close it would work fine.

Spent days trying to make it work (it would work, then lose the connection, roaming was probably an issue too) and in the end leased meraki hardware that worked fine.

I'd avoid their cheap tier of AP at least.

Activists 10 years ago are probably still linked to interesting people the government wants to survey though, even if they are maybe less active now

Activists typically aren't secretive about their actions, on the contrary they tend to be as public as they can safely be. The setup though might be, if it's to prepare an event that might be crushed down before it even take place, but then even a day later, not even a decade, to decipher would be too late and thus pointless.

We departed around 30-45 min late from Basel sbb (in Switzerland) in a night train that goes through Germany.

They told us about the communication issues but what surprised me is that they told us that the Deutsch bahn replaced the locomotive with one of their (that was near the border I guess) so we could depart.

That's something I did for small medium size data analysis (300Gb of csv). The reported size was around 800gb with indexes iirc and it fitted on a 512gb SSD.

It compresses the indexes pretty well but don't forget to turn off postgres' own copy on write mechanism

You probably are compared to your baseline self (another comment goes more extensively on this subject) but maybe you have enough driving skills and common sense to minimize the risks somewhat.

Please this is not reddit

Do you make SoMs for a reseller by any chance ?

I'm looking at the newest versal chips from Xilinx/AMD for a new design and buying a SoM & designing our carrier board could fit the bill nicely. We're still very early in the design process, we need to get prices for the chips too to see if it's an idea worth pursuing.

Sorry just saw this. I don't make "conventional" SoMs, but I could help you with some information. What sort of quantity are you looking for?

I don't often post here (I forgot to check the guidelines), should I have left the original title "(bcachefs) Trouble in the kernel" ?

While the article that follows is well written, the original title feels very vague and clickbaity for me. Like "you won't guess what's wrong with this !!!".

I felt this give a much better idea of the content (technical problems that exposed people problems) and give chance to people that don't want to read about kernel politics / drama a chance to skip the article.

Maybe because people seem to be very emotional about this right know? I'm myself not sure if this is related to the woke mind virus or Kent being a dick

We only have the point of view of becachefs main developer here of course, but some things regarding some kernel developer and the CoC committee seem to be really concerning.

What are you concerned about? Kent's continuous, repeated assholery got flagged up to the CoC committee, who took appropriate action.

This is why we have CoCs. This is why we need CoCs.