dybr

 Hey, I'm on a "customers cases".

One case, which I was pinging for several days, was that a user updates her phone number (it's "her" IRL), but the phone does not get updated.
When you dive deep in the server code, you see that this update is sent to some quasi-external service, that service returns an error, we don't log the error message, but just a warning, like "a condition was not met", and return another error to the client, which client ignores the error, happy to have received an answer.

OTOH, the service does log the errors received. In a table in a database. I spent some time trying to log in to production postgres, and I did, but I had no clue which database to use; probably the postgres was the wrong one. I know how to switch databases and list tables in postgres (and I love postgres), but well.

Eventually I had tracked x-request-id, and found that the external service returns "risk too high". While when we send them a request, we set "HighRiskAllowed="highriskallowed". FIIK if this is a good boolean value anyway. But I was happy to kick the ball over the fence. But before that I read through the OPS jira case and found that this was all already discovered by another team, a month ago. So, wtf, right? 

Another problem I was supposed to investigate was when a user is allowed to access his account without any trace of EULA signed. Oh, whatever. Left it for Esteban to investigate.

Oh, and besides. I planned to deploy one service to prod today. And asked Mike to approve. Mike approved it. But then the build system told me that the approval stage had an error. There is a log. The logs says: "delayed for 5 seconds... called a script... called a script... delay another something..." etc. No trace of error in the log.

But then another build was ready, the one where a comment line was removed by Bill. So I suggested Mike to approve this one, while I'm bugging the Jenkins guys (if they'll ever bother to react).

In short, I had a lot of time to watch movies. Like, e.g., ypq does, right?

A day off tomorrow. AFK. Away From the Keyboard.