May. 28th, 2024

dybr

May. 28th, 2024 06:41 am
juan_gandhi: (Default)

(это просто перевод одной записи дыбра за прошлый год, игнорируйте) 

Today it's supposed to be a holiday, but I'm a contractor, my holidays are unpaid, and I have nothing else to do, so I worked.

So, what's up? Worked on a couple of Jira cases; wrote to Bermy (not sure about his name's spelling). BTW, I'm not the only one working. There was a case, sent to me by a bot, where tests are failing; I had reassigned it to Sam, saying that I'm not aware of the context. Sam is a contractor in Canada, by the way. Sam found that this "style error" is a new, recently added check: we should not use `unapply` in case statements. Well, that's reasonable. Sam wrote something like that to me and to someone else too; I thanked here on Slack, great idea - and approved it. We are competing in our show-off, or something. Well, or is she's just young and likes fighting? I only fight against blocking my progress, otherwise I can't expect a promotion, and I don't care. I'll rather diversify my entertainments.

 

 

dybr

May. 28th, 2024 08:36 pm
juan_gandhi: (Default)

Ok, so, a day after a long weekend is still a long weekend.

What did I do? Since Sam approved yesterday my rather old PR (seems like we are buddies now, flattery works),
I decided, ok... I have to move on to the next project to automatically document.

But wait, there was this weird rather old jira case, when a user changed her (I know it's 'her') email, she still was getting mails to her old address. (Is not it typical?) - so it was my duty to investigate. I looked around. I don't know how many servers we have. There is no "hound" that would search over the whole repo. I can do `rg` (a much faster version of grep) in the projects that I had pulled on my machine; found tons of records containing emails, in classes like 'UserV2', 'UserDigest', etc. So I decided, let me ponder on all this. And went shopping.

After returning from shopping, I decided that instead of doing this lonely prospecting, I'll ask the people. And went doing something, while slapping together a list of questions to ask. Like, where the shit is "our" database"? Which of "our" services deal with "users" emails? Etc. Add these questions to Jira, and ask on Slack.

Oh, and also, there's some app on my work machine that controls which version of what we have, and it wanted me to reconnect to the main system. And I tried and tried. No, it does not work. I posted this on a tech support channel, and a bot basically copied my question and asked if it was resolved. I said "no". That was the end of the support track. Also, this app told me to upgrade Chrome. I did. Chrome restored a session, partially, and then just hung. 

So I took a break, then went back and rebooted. That's how I spent some time...

Also, I got back to that doc generation. First I wanted to reproduce the functionality that was so smoothly working before. No, it did not. Weird messages. Took me some time to figure out that my github token ("PAT" it's called) was expired. Not a problem, I generated another PAT. Still not working. Took me some time and googling (ok, git is REALLY good at pointing not only at the error, but also at its docs). Turned out I had to reauthorize the company to let it use my new token. Done.

By that time, instead of running my simple script called `r`, I was running a less simple script, the command was `run (project name)`. Bad name, btw, it's not `run`, it's `document` or something. Will have to figure out.

Then I spent an hour or more trying to figure out wtf is going on now. github was not returning tags for the project, it was just telling me that there's nothing there. So I used another github endpoint, to list the projects. That worked. So, wtf, right? Can I just pull (or git clone) the project? No. And why so? Because of a typo in the project name.

So I updated the script, to react properly to a bad project name. Then I felt a bit better.

And then it all worked; and while it was generating, I looked into other things... and then came the "standup".

Shared our weekend experiences. Bill, in Florida, rode 56 miles on his bicycle, with the air temperature close to 95 degrees. Etc. It's heroic. I don't think I'll go biking in the temperature above 85.

At the meeting I shared my troubles with "user email" - I expected to be pointed at the docs, etc. No. Bill and Brad opened some pages on their computers, tried to find the history of changes, and could not. So they told me this: go to Capybara people (that's a team, Capybara is their totem), and ask them whether they can find this change in email, the messages sent, and, basically, ask them to take care of this problem.

I like this approach! Not our business! Delegate! Cool. Will do.

But first, I spent time looking up Capybara's slack channel. There exists one, but it's archived. So I asked first, on our common channel, whom to ask and where. And that was the end of my day.

Well, not exactly. In the case where exceptions are logged one line per message, Brad showed me an example how it happens (in `fs2`, but I don't know how it's related... but I'll try to reproduce anyway). Tomorrow. I just took a snapshot of the datadog screen.

Tomorrow, tomorrow.

Profile

juan_gandhi: (Default)
Juan-Carlos Gandhi

October 2025

S M T W T F S
    1 23 4
5 678 9 1011
12 13 1415 161718
1920 2122 23 2425
262728293031 

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 25th, 2025 12:04 am
Powered by Dreamwidth Studios