Hello! I just started crunching this project a few days ago and drilled a bit through the logic and plausibility of the whole infrastructure. It's great!

Today, I found what seems to be a reporting error concerning the overall task run time (et) (not CPU time, ct):

$ grep     yafu_ali_3019266_L144_C134_1734494706_18_1 /var/lib/boinc-client/job_log_yafu.myfirewall.org_yafu.txt 
1734702315 ue 4070.213696 ct 48933.680000 fe 1349591422494400 nm yafu_ali_3019266_L144_C134_1734494706_18_1 et 3804.080444 es 0

$ journalctl -u boinc-client.service | grep        yafu_ali_3019266_L144_C134_1734494706_18_1
Dez 20 13:41:49 hyperv-ryzen boinc[1259]: 20-Dec-2024 13:41:49 [yafu] Starting task yafu_ali_3019266_L144_C134_1734494706_18_1
Dez 20 13:41:49 hyperv-ryzen boinc[1259]: 20-Dec-2024 13:41:49 [yafu] [cpu_sched] Starting task yafu_ali_3019266_L144_C134_1734494706_18_1 using yafu-8t version 13401 (8t) in slot 0
Dez 20 14:45:14 hyperv-ryzen boinc[1259]: 20-Dec-2024 14:45:14 [yafu] Computation for task yafu_ali_3019266_L144_C134_1734494706_18_1 finished

Task: https://yafu.myfirewall.org/yafu/result.php?resultid=9192117

Created 	19 Dec 2024, 21:39:37 UTC
Sent	 	20 Dec 2024, 0:53:30 UTC
Report deadline 2 Jan 2025, 10:07:14 UTC
Received 	20 Dec 2024, 13:45:22 UTC
Run time 	12 hours 51 min 52 sec
CPU time 	13 hours 35 min 33 sec 

WU: https://yafu.myfirewall.org/yafu/workunit.php?wuid=7848379

46,312.00 (Run time (sec) = et)
48,933.68 (CPU time (sec) = ct)

So the client job log has logged a task run time of 3,804.080444 seconds, confirmed by the start and finish times in the systemd journal, but the server has logged 46,312.00 seconds instead.
Sadly I didn't catch the factor.log to see if the wrong time was buried there.

Edit:
It seems to match the server side delta of the send and receive times:
[2024-12-20 13:45:22] - [2024-12-20 00:53:30] = 46312 sec
That's new. Why in this instance, and why not for many other tasks?

The tasks are like quests and the credits are like surprise crates 😅 It's a real lottery how much you get.
Maybe because of some statistical chaos with the new app, this takes the cake:

https://yafu.myfirewall.org/yafu/result.php?resultid=9214108

Run time 	11 sec
CPU time 	14 sec
Credit 		119.84

https://yafu.myfirewall.org/yafu/result.php?resultid=9214333

Run time 	3 hours 10 min 28 sec
CPU time 	1 days 16 hours 58 min 47 sec 
Credit 		127,774.34

https://yafu.myfirewall.org/yafu/result.php?resultid=9215529

Run time 	3 hours 59 min 5 sec
CPU time 	2 days 5 hours 7 min 57 sec
Credit 		156,519.73

An inverse case, double the work, 100 times less credits:
https://yafu.myfirewall.org/yafu/result.php?resultid=9213247

Run time 	8 hours 48 min 27 sec
CPU time 	4 days 20 hours 39 min 26 sec
Credit 		1,796.24

All with Application version YAFU-16t v212.01 (16t)

The now active pattern seems to be a consistent factor of around 11 credits per run time second starting between 7:00 and 18:00 yesterday (2024-12-27). Like 100 times more credits than before, at least for the 16t variant. I'm not complaining 😁