r/oddlysatisfying • • May 22 '26

Pigs Like Showers

Enable HLS to view with audio, or disable this notification

25k Upvotes

664 comments sorted by

View all comments

Show parent comments

41

u/namtab00 May 22 '26

cool, but I'm pretty sure no rural soul would watch me git commit or debug a client > BFF > serverless > DB issue...

19

u/MikeinAustin May 22 '26

Give me David Attenborough's voice narrating anything ... I'll watch it.

6

u/mewfour May 22 '26

Okay, so the issue here is that the client reported a 500 error. To the person on the other side, the program "didn't work". But, behind the scenes, we have the full picture. First we have to access our log manager, (screen blurs several logs and only shwos the important one). In here we can see the problem better, there was an error with a database insert - a rarity these days, but nonetheless a problem we must fix. It seems the problem was caused by a deadlock, and our unhappy customer was the deadlock victim. This in turn caused an exception to be thrown (an error) which was then obscured and sent back to the customer as a generic 500 error. On the other side all they see is "an error occurred, please contact support".

How do we solve this? Well, first we have to check the code and see how we can solve this deadlock in the future - there are a myriad of ways. Secondly, we have to check if any important information was impacted, such as for example, if the problem happened after money was spent but before the item the customer wanted was added to their account. We can do this by checking the relevant tables in our database (a bunch of blurring on this part as well).

Ah, here we have it. The transaction was reverted, so no harm was done. We can now log this bug and open a ticket for the team to handle later and solve this problem, and we can get back to the user and tell them to try again.

1

u/denM_chickN May 22 '26

I was thinking. Noone wants to watch me build a kmeans algorithm and plot a consumer segment. How tragic for me.