долой дискомфорт

 Вот тут три линка: на Петрановскую, Марголис, и еще одного, не знаю, кто такой.

Короче, страдающая Россия. Как им там тяжело без поездок в Европу, с упавшими ценами на недвижимость, с ухудшением качества снабжения. И никто не сочувствует. Уже не говоря о том, чтобы помочь материально.

Кто-то их обижает. А, Путин их обижает. И мальчиков ихних. (Кто на самом деле обижает ихних мальчиков, они только между собой обсуждают, а на публику стесняются выразить свое возмущение коварными украми.)

dybr

 Ok, so nobody approved my small PR, and I decided to work on that memory leak.

 

We also had a "standup", where two new guys were introduced, and we basically said good bye to Jorge, a Bolivian Scala ZIO guru. One new guy is from the North of North Carolina. A pretty curious enthusiast, hope he'll make it.

 

Then I switched back again to the memory leak - started writing a "report memory" method - just wrote the name, as suddenly copilot wrote the rest of the code. I only refactored it a bit, to keep values lazy.

 

Ran the app (ok, for that I had to update the version of the load-testing infrastructure, never met it before, and it was not compatible with Scala 2.13, which was in that service. No big deal, upgraded, fixed some code (naming, etc), and I observed the memory leak, when I launch the server and pummel it with the load tester. Perfect. Now I have to find the culprit. But since it is WSDL and XML, these two usual suspects will be investigated.

 

Updated the Jira case, to properly inform the people.

 

Qian even reviewed that code (88 files, because of "copyright year change". No big deal.

 

That's it; worked a little bit in the airport, because I'm on my way.