05:01:20 <selsta> moneromooo: you can change the build.yml file to http://paste.debian.net/hidden/8828e699/ to debug the issue
07:50:53 <ErCiccione[m]> xiphon: any idea of why the "donate" button in my ccs proposal is broken? https://ccs.getmonero.org/proposals/erciccione-website1.html the number of the proposal is missing when clicking the button.
11:55:39 <xiphon> ErCiccione[m]: looks like it fails to generate the donation address
11:56:34 <ErCiccione[m]> yeah but i don't see any obvious reason for that behaviour
11:58:11 <xiphon> for example, the obvious reason would be the wallet being down
12:01:26 <xiphon> the one running the ccs backend (or having an access to it) could run the following command and inspect the errors in the output
12:01:30 <xiphon> php /var/www/html/ccs-back/artisan generate:addresses
12:06:11 <ErCiccione[m]> i'm not sure but binaryfate or luigi1111 might have access
12:32:23 <xiphon> pigeons and fluffypony might as well. But i'm not sure of the current state
12:51:50 <binaryFate> checking
12:55:03 <binaryFate>  RuntimeException  : Connection to node unsuccessful
13:07:59 <binaryFate> we're looking into this
14:08:05 <moneromooo> selsta: https://github.com/monero-project/monero/pull/6433
14:08:49 <selsta> iDunk: can you also test ^
14:08:52 <selsta> moneromooo: ty
14:12:04 <moneromooo> tbh this timestamp change feels a bit weird. It means you can't use incrementing nonces, which means you have to have correct timekeeping.
14:12:33 <binaryFate> xiphon ErCiccione[m] ccs wallet should work now
14:12:33 <moneromooo> Before that patch, using 1, 2, 3... would have worked. Not sure how common it is to have bad timekeeping nowadays.
14:13:19 <niocbrrrrrr> binaryFate: working thx
14:14:33 <ErCiccione[m]> binaryfate: Thanks
14:14:43 <xiphon> (y)
14:56:07 <iDunk> moneromooo: This is from a test last night  https://paste.debian.net/hidden/51bd75c4/
15:00:06 <iDunk> It gets a bit further with 6433  https://paste.debian.net/hidden/ee487d70/
15:30:56 <moneromooo> It now works reliably for me.
15:36:11 <moneromooo> Do you have a log-level 2 for the daemon (monerod1.log, not the usual monerod0.log)
15:37:15 <moneromooo> Hmm. Your line numbers don't match mine. I might have mixed something up...
15:39:43 <iDunk> I added logging lines.
15:40:30 <iDunk> Latest test  https://paste.debian.net/hidden/b9d70ef7/
15:49:29 <moneromooo> And what's in monerog1.log ?
15:49:32 <moneromooo> (ll2)
15:59:51 <iDunk> https://paste.debian.net/hidden/246e600e/
16:02:29 <iDunk> Are those epoch timestamps ?
16:02:32 <iDunk> $ date -d @1586188692867165
16:02:32 <iDunk> 16 Sep 50266288 18:52:45
16:03:31 <moneromooo> Microseconds.
16:03:38 <iDunk> Ah
16:03:47 <moneromooo> Your computer is too fast and generates two signatures in the same microseconds I think.
16:03:54 <iDunk> Ty :)
16:03:56 <moneromooo> I will fix :)
16:06:01 <moneromooo> Does https://paste.debian.net/hidden/68d60bf7/ help ?
16:09:51 <iDunk> First run completed without issue :)
16:10:43 <moneromooo> So now we know generating a sig takes less than a microsecond on iDunk grade hardware :)
16:11:24 <iDunk> It's an old Ryzen :)  Would that patch help selsta, instead of 6433 ?
16:12:13 <moneromooo> No, we need both.
16:12:37 <moneromooo> I pushed that to 6433 too.
16:13:45 <iDunk> 5/5 passed, I call it fixed.
16:13:52 <moneromooo> Thanks.
16:13:58 <iDunk> Yw