02:54:25 <v01dPirate[m]> <3 devs
07:26:44 <netrik182> selsta erciccione did you happen to remember the lupdate command we spoke some time ago?
07:27:12 <netrik182> Or maybe you have pointers on how can I figure it out? Thanks
08:57:13 <selsta> netrik182: I'll check tomorrow in my irc logs, but if it's not in the logs then I don't have it
09:11:11 <netrik182> Ty
09:11:15 <ErCiccione> netrik182: the only one i can find is `lupdate qml.qrc -ts translations/monero-core.ts -no-obsolete && lupdate qml.qrc -ts translations/monero-core_*.ts -no-obsolete`
09:13:01 <ErCiccione> actually, i think that's the correct one, because the old one worked with the `.pro` file, that it's not used anymore
13:07:56 <netrik182> Right, at monerologs.net I found one that used .pro so this one is surely different 
13:08:10 <netrik182> I can't test right now but will do it later
17:54:39 <selsta> ErCiccione: that looks correct
21:55:53 <selsta> moneromooo: any idea re https://github.com/monero-project/monero/issues/8142 ?
22:00:03 <moneromooo> It's done on a timer IIRC (kinda).
22:00:31 <moneromooo> IIRC, when adding a new block, it goes through the checks if last check was > some threshold.
22:01:00 <moneromooo> I see the reporter did not mention any period for that behaviour.
22:03:23 <moneromooo> 20 seconds to go through all is scary slow though, so maybe 20 seconds is the period, and the first and last messages are not part of the same set.
22:04:16 <moneromooo> The code shows the delay for the file based checkpoints is 10 minutes.
22:06:04 <moneromooo> The only reason I can think of for rapid repeats is if there's an exception after checking, which skips seting the "last check" time. But you'd have a stack trace in your log, unless you built without libuwind.
22:09:58 <moneromooo> I added a comment.