Colleague fucked up the production NoSQL DB of a customer 15 minutes before the workday would be over... I stayed to help him out. An hour in now, Wish us luck.😞

If I was your colleague, I would probably feel so shitty for what ever mistake he made :/
...at least someone is helping him.

Yea he feels miserable, another colleague also stayed, we told him not to worry, all data seems to be recoverable, just allot of manual work.

He got us Pizza 😋

You're a good man. Good luck man

@busuu yea he is

@Condor last one was 2 days ago, so that was not an option

In the end it costed the 3 of us 3 hours and it was not even fully the colleague fault.

Abstract explanation what happend:
Colleague created the following function:
For collection of X that are not in collection Y Create A.

Colleague did not knowing that collection Y could not be bigger than 128. So when X was bigger than 128 for the overflow would another set of A be created.

However X may only have one A so the older A got archived. A also managed a Collection of B that also got archived with some where already archived

This resulted in near 1000 documents needed to be adjusted.

But we had a good workflow, the colleague found out which Xes was tempered, then the other colleague would find the old A, then gave me the id of A so I could find the collection of B so I could unarchive some of the B's.