00:46:45 "> <@dalek:anontier.nl> Meh, I'..." <- But hey. Wrong place for all of this 02:47:23 Guys, somebody knows how I can generate test binaries for `debug` 02:47:28 s/`/`?/ 02:47:34 * jrandom[m] uploaded an image: (101KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/yjlxaeKvQvgegmwXLDdyrCGY/image.png > 02:48:41 There's no `tests` folder inside the `debug` folder, and therefore I can't run `make [-jn] debug-test` 02:48:48 Any ideas about how to fix this? 02:49:29 s/binaries/files/, s/`/`?/ 02:50:27 I'm able to run `make release-test` without problems. 03:15:13 jrandom[m]: it's a release branch so maybe tests are disabled 03:23:44 jrandom[m]: what do you mean you can't run make debug-tests? 03:24:49 release branch is fine for tests 03:26:19 selsta: When I run `make debug-test` I get this message: 03:26:22 * jrandom[m] uploaded an image: (119KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/ueOehXmACWcaDxsbaRYrLFTc/image.png > 03:28:00 Maybe is related to what UkoeHB said, and no `debug` tests were generated because I'm using a release branch? 03:28:54 on the readme inside `monero/tests/` it says: 03:28:59 * jrandom[m] uploaded an image: (64KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/OpBaQWEjLXhvKfNknpLscbHa/image.png > 03:29:44 I'm basically doing all of this because I want to be able execute/debug each test individually. 03:32:58 I mean, just defining a breakpoint and be able to see the stackframe of the test 03:33:04 * jrandom[m] uploaded an image: (125KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/OGoLxhkLopUSwbdpduPhlDtZ/image.png > 03:34:00 jrandom[m]: did you do changes to makefile or cmake files? 03:34:28 `make debug-tests -j10` works fine here 03:34:55 also in which folder are you when running `make debug-tests` ? 03:35:41 I don't think so, maybe I messed up in some build step 03:35:51 I'm trying to run it in the root `monero` folder 03:36:01 ok, that should be fine 03:36:47 testing release branch too now 03:37:11 Alright, thanks 03:39:59 works here https://paste.debian.net/plainh/82025c3d 03:41:00 Ok, thanks a lot, really, I guess I'll have to verify the build process again 03:42:33 just to clarify, you did `make debug-test` right and not `make debug-tests` ? 03:42:54 I wrote it wrong in the last messages 03:43:47 No worries, yes, I ran it without the `s`, `make debug-test` 03:44:52 I would try a fresh clone and then just `make debug-test` directly from the command line 03:45:49 Alright, let me give it a try 06:05:52 make -C build/something/debug/wherever/tests/unit_tests test 06:06:35 cmake must be run with BUILD_TESTS=ON, which make {debug,release}-test does. 11:22:04 I got the error "MoneroRpcError: Request timed out in 30000 milliseconds" when I use the js library 11:22:14 How do I configure the timeout number? 12:07:26 Well here is the bug. First I export all the outputhex from a view-only wallet. Then I import it to the cold wallet and sign it and export all the key images. If I import all the keyimages(with signatures) to the view-only wallet it is fine. but if I only select, say, the last three keyimages(with signatures), it returns an error. 12:08:38 This is the request. I chopped the whole array and only input the last three keyimages:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/1cdfc8669c7cbd939e1a561930a50b10dbb5e3bc) 12:08:43 This is the error: 12:09:49 `... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/18a9315e739d6c35a9e706f42393b0a0510befce) 12:11:30 Why is the signature check failed? 12:40:22 Because you omitted some of the key images ? It's out of sync since you removed some. 12:40:42 It'll try to verify data from the an output with the key image from another. 12:41:13 You'd have to include an extra offset to tell the imporer how many to skip. 12:41:27 (or, if there is one already, modify that offset to match what you removed) 17:00:11 Currency doesn't necessarily mean capitalism lol 19:34:20 moneromooo: how to fingerprint a node? i want to identify a particular node regards: when it is up and for how long 19:34:47 problem is the node is transient and moves locations .. 19:35:45 can settings, height, or else be used for identification? 19:35:45 if anyone has info, please chim in 19:39:20 Everything you can think of. 19:40:54 And if you find good ways, please list them here :) 19:41:26 An obvious one is height. When it comes back online, it'll start syncing from its old height. 19:41:40 Someone wanted to add a "release" flag. That can be used too. 19:41:48 RPC version. 19:42:09 The set of txes it has in its txpool. 19:42:18 (though that takes active probing) 19:42:47 Go through message request/response structs and think. 19:43:03 both height and mempool change quickly after the node goes online, so it can only work if it connects to the same IPs it used before 19:43:05 moneromooo: Can we make monerod pop random amount of blocks when restarting ? 19:43:08 You can also fingerpring the OS. 19:43:12 Yes. 19:45:12 * > <@moneromooo:libera.chat> An obvious one is height. When it comes back online, it'll start syncing from its old height. 19:45:12 Can we make monerod pop random amount of blocks when restarting ? 5-100 blocks just to avoid finger printing 19:45:29 The "yes" was for you. 19:45:56 I made the wallet do that already. It doesn't actually pop, but requests blocks from an earlier quantized height. 19:46:25 moneromooo: When connecting to remote nodes ? Nice 👌 19:46:31 If you're good, you might still be able to guess the real height from timing though. 19:46:57 Can't recall whether done for untrusted only. That was a long time ago. 19:47:25 Back when I cared about leaks to third party nodes :/ Unintended consequences... 19:54:57 "Go through message request/..." <- since it popsup somewhere with close 0% change to catch within first hours and likely offline before 24h pass, my Q is directed to static info 19:55:25 the node is standard latest github release bin for linux