libera #monero-dev

23 Oct 2023

Official repo: github.com/monero-project/monero || Don’t ask to ask, just ask:) || Monero GUI dev is at #monero-gui || Monero website dev is at #monero-site || Non-dev questions -> #monero, please || No fork help, you’re on your own

• 12:00
  selsta
  is anyone running self compiled v0.18.3.1 (not release binaries or depends build system) and had issues with daemon losing connection to other peers?
• 12:16
  selsta
  (after a couple days uptime)
• 21:13
  gingeropolous
  nope: Height: 3002432/3002432 (100.0%) on mainnet, not mining, net hash 2.86 GH/s, v16, 12(out)+36(in) connections, uptime 20d 10h 33m 33s
• 21:13
  gingeropolous
  selsta, thats my homebox. this is xmrchain: Height: 3002432/3002432 (100.0%) on mainnet, not mining, net hash 2.86 GH/s, v16, 124(out)+128(in) connections, uptime 20d 10h 29m 32s
• 21:15
  selsta
  gingeropolous: ty. i worry that it might be related to a specific version of a dependecy. (assuming this bug even exists)
• 21:15
  selsta
  there were 2 reports of a self compiled v0.18.3.1 daemon having issues, but it might have been coincidence
• 23:42
  fvok4
  jeffro256, you said to run tests/performance_tests/performance_tests. I did and it worked fine. Now, where can I find the meaning of the parameters used in the tests?
• 23:44
  fvok4
  for example, "test_sig_clsag<64, 2, 2> (1000 calls) - OK: 37752 µs/call" and "test_construct_tx<100, 10, true> (5 calls) - OK: 227 ms/call". What do the parameters within "<" and ">" mean?
• 23:44
  fvok4
  right now, I'm reading the source code, trying to figure it out, but I'm unsure