-
v01dPirate[m]<3 devs
-
netrik182selsta erciccione did you happen to remember the lupdate command we spoke some time ago?
-
netrik182Or maybe you have pointers on how can I figure it out? Thanks
-
selstanetrik182: I'll check tomorrow in my irc logs, but if it's not in the logs then I don't have it
-
netrik182Ty
-
ErCiccionenetrik182: 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`
-
ErCiccioneactually, i think that's the correct one, because the old one worked with the `.pro` file, that it's not used anymore
-
netrik182Right, at monerologs.net I found one that used .pro so this one is surely different
-
netrik182I can't test right now but will do it later
-
selstaErCiccione: that looks correct
-
selstamoneromooo: any idea re monero-project/monero #8142 ?
-
moneromoooIt's done on a timer IIRC (kinda).
-
moneromoooIIRC, when adding a new block, it goes through the checks if last check was > some threshold.
-
moneromoooI see the reporter did not mention any period for that behaviour.
-
moneromooo20 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.
-
moneromoooThe code shows the delay for the file based checkpoints is 10 minutes.
-
moneromoooThe 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.
-
moneromoooI added a comment.