…but … but according to background, the bug photo comes from a different log than you were looking at.
please make sure to report the bug to the correct team.
closed/wontfix! 🤡Looks like you need to invert a binary tree.
what does logrotate look like? lol
I think they don’t need logrotate, they need the exact opposite: logdontrotate
that looks more like journalctl -r lol
knowing where something happens is not knowing what happens and especially not knowing why it happens.
A big import of data caused a specific datapoint to be inserted twice into the database, but that only happened in our shared testing environment not in our development environment, logs made it clear that we tried to insert something twice into a join table but not why.
the fix was easy, we can remove the duplicated datapoint from our data before writing it to the database, and we found an edgecase we can handle further upstream so we don’t end up duplicating it in the first place, but why didn’t we run into this issue in dev?
the data is consumed from a kafka topic with a single partition and read order is allways the same as write order, so our service behaves the same way if the same data is written to the topic everytime, but it turns out the producer does not necessarily write in the same order to the topic given the same input and gaining that understanding was a goose chase with debuggers, logs and combing through code of multiple services written by multiple devs working at multiple companies and thats the true horror of enterprise development jobs, teying to get someone from a different team or even company on the phone who can actually explain something to you with whom you can analyse a bigger part of a system.
