01:21:30 UkoeHB maybe a Ctest bug?? https://github.com/Maratyszcza/NNPACK/issues/120 , https://github.com/BhallaLab/moose-core/issues/365 01:21:55 Is it reproducible ? 01:24:06 jeffro256[m] it doesn't happen on my machine so idk 01:56:44 UkoeHB: maybe you can add some extra logging to the seraphis_serialization_demo.seraphis_squashed_empty test to see why it fails? 01:59:53 here's what I get 01:59:54 [----------] 2 tests from seraphis_serialization_demo 01:59:54 [ RUN ] seraphis_serialization_demo.seraphis_squashed_empty 01:59:54 Floating point exception (core dumped) 02:00:39 could be divide by zero for example 02:01:26 that's nearly the only cause of FPE these days 02:02:37 divide by zero in serialization? 02:02:52 it's serializing an empty tx in that test 02:07:01 Shouldn't a divide by zero be caught and handled like a normal exception with google test ? I.e. it should just fail a specific test? 02:11:51 Stack trace: https://paste.debian.net/1257675/ 02:12:04 and looks like `num_bin_members` is 0 here: https://github.com/UkoeHB/monero/blob/1e167ddc17a44ac15c0c7750d22d24a3d1bfb129/src/seraphis/tx_component_types.cpp#L102 02:19:21 jberman[m]: oh that would do it 02:19:57 wonder why it works on my machine... 03:36:30 .merges 03:36:31 -xmr-pr- 8319 8355 8516 8517 8525 8527 8529 8543 8564 8569 8570 8571 8578 8580 8590 8593 8594 04:08:25 hey i had a question abt hostin a public node over tor. i got a synced node correctly connecting over clearnet, but when i run a torsocks command to check connection over tor it says my address cannot be resolved. did some digging around online without luck. any advice for this? 04:25:56 This makes me feel like my configuration may be correct, but my node-peers may be unstable? "Guard poiuty is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also but it could also mean an attack against you or potentially the guard itself. Success counts are 71/151. Use counts are 0/0. 136 circuits completed, 0 were unusable, 65 collapsed, and 106 timed out. For reference, your 04:25:56 timeout cutoff is 81 seconds." 04:26:24 s/Success counts are 71/151. Use counts are 0/0. 136 circuits completed, 0 were unusable, 65 collapsed, and 106 timed out. For reference, your timeout cutoff is 81 seconds.// 04:29:44 * This makes me feel like my configuration may be correct, but my node-peers may be unstable? "Guard poiuty is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also but it could also mean an attack against you or potentially the guard itself." 04:30:29 * This makes me feel like my configuration may be correct, but my node-peers may be unstable? "Guard poiuty is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also but it could also mean an attack against you or potentially the guard itself." I'm silly, was looking at the tor logs of me trying to connect to my node. Of course a lot of circuits were failing... 14:25:56 Any ideas about this error? https://www.reddit.com/r/MoneroMining/comments/y7omwg/what_does_this_error_message_mean_running_latest/ 15:41:13 sech1: whatever issues they have seems unrelated 15:41:36 it's like you said someone sending invalid data