dybr

Basically, I was supposed to investigate and document that "magic link" stuff, but there was a case that Janet asked me to do, so...

So, that piece was even simpler: remove "internal/" from the uri. So I did, big deal. And updated the test case.

And it failed in Jenkins. And I rolled it back, and it did not fail. I replaced "internal" with "infernal" - it fails.

More, Jenkins did not show me which test fails, and what's the problem. I asked colleagues, and Sam told me that there's a button in Jenkins runs, where I can see specifically test runs results.

Ok, good. And the failing test has nothing to do with what I did. It was even a different suite.

The "solution" was not to rename my specific test case, but add some text in the end of the name. Then everything works.

Otherwise one "mock" (in God knows which test suite) tells me that it expected an array of about 200 records (all shown in the test log), but it did not receive anything. And if I rename my test case, it works ok.

See, it's mock, so blaming improperly reinitialized postgres in docker also makes no sense.

But I liked the fact that I hacked this shit. So I took a break.

And then, later, I worked on my docs.

That's it for today. You probably guess what kind of company it is. With all that "functional scala programming", with monad transformers, "Kleisli functions", etc. Monkeys typing War and Peace. No, Warren Piece.