-
w[m]
<Elijah[m]> "> <@dalek:anontier.nl> Meh, I'..." <- But hey. Wrong place for all of this
-
jrandom[m]
Guys, somebody knows how I can generate test binaries for `debug`
-
jrandom[m]
s/`/`?/
-
-
jrandom[m]
There's no `tests` folder inside the `debug` folder, and therefore I can't run `make [-jn] debug-test`
-
jrandom[m]
Any ideas about how to fix this?
-
jrandom[m]
s/binaries/files/, s/`/`?/
-
jrandom[m]
I'm able to run `make release-test` without problems.
-
UkoeHB
jrandom[m]: it's a release branch so maybe tests are disabled
-
selsta
jrandom[m]: what do you mean you can't run make debug-tests?
-
selsta
release branch is fine for tests
-
jrandom[m]
selsta: When I run `make debug-test` I get this message:
-
-
jrandom[m]
Maybe is related to what UkoeHB said, and no `debug` tests were generated because I'm using a release branch?
-
jrandom[m]
on the readme inside `monero/tests/` it says:
-
-
jrandom[m]
I'm basically doing all of this because I want to be able execute/debug each test individually.
-
jrandom[m]
I mean, just defining a breakpoint and be able to see the stackframe of the test
-
-
selsta
jrandom[m]: did you do changes to makefile or cmake files?
-
selsta
`make debug-tests -j10` works fine here
-
selsta
also in which folder are you when running `make debug-tests` ?
-
jrandom[m]
I don't think so, maybe I messed up in some build step
-
jrandom[m]
I'm trying to run it in the root `monero` folder
-
selsta
ok, that should be fine
-
selsta
testing release branch too now
-
jrandom[m]
Alright, thanks
-
selsta
-
jrandom[m]
Ok, thanks a lot, really, I guess I'll have to verify the build process again
-
selsta
just to clarify, you did `make debug-test` right and not `make debug-tests` ?
-
selsta
I wrote it wrong in the last messages
-
jrandom[m]
No worries, yes, I ran it without the `s`, `make debug-test`
-
selsta
I would try a fresh clone and then just `make debug-test` directly from the command line
-
jrandom[m]
Alright, let me give it a try
-
moneromooo
make -C build/something/debug/wherever/tests/unit_tests test
-
moneromooo
cmake must be run with BUILD_TESTS=ON, which make {debug,release}-test does.
-
willshu[m]
I got the error "MoneroRpcError: Request timed out in 30000 milliseconds" when I use the js library
-
willshu[m]
How do I configure the timeout number?
-
willshu[m]
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.
-
willshu[m]
This is the request. I chopped the whole array and only input the last three keyimages:... (full message at
libera.ems.host/_matrix/media/r0/do…8669c7cbd939e1a561930a50b10dbb5e3bc)
-
willshu[m]
This is the error:
-
willshu[m]
-
willshu[m]
Why is the signature check failed?
-
moneromooo
Because you omitted some of the key images ? It's out of sync since you removed some.
-
moneromooo
It'll try to verify data from the an output with the key image from another.
-
moneromooo
You'd have to include an extra offset to tell the imporer how many to skip.
-
moneromooo
(or, if there is one already, modify that offset to match what you removed)
-
IC_XC_NIKA[m]
Currency doesn't necessarily mean capitalism lol
-
drflashd[m]
moneromooo: how to fingerprint a node? i want to identify a particular node regards: when it is up and for how long
-
drflashd[m]
problem is the node is transient and moves locations ..
-
drflashd[m]
can settings, height, or else be used for identification?
-
drflashd[m]
if anyone has info, please chim in
-
moneromooo
Everything you can think of.
-
moneromooo
And if you find good ways, please list them here :)
-
moneromooo
An obvious one is height. When it comes back online, it'll start syncing from its old height.
-
moneromooo
Someone wanted to add a "release" flag. That can be used too.
-
moneromooo
RPC version.
-
moneromooo
The set of txes it has in its txpool.
-
moneromooo
(though that takes active probing)
-
moneromooo
Go through message request/response structs and think.
-
sech1
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
-
nikg83[m]
moneromooo: Can we make monerod pop random amount of blocks when restarting ?
-
moneromooo
You can also fingerpring the OS.
-
moneromooo
Yes.
-
nikg83[m]
* > <@moneromooo:libera.chat> An obvious one is height. When it comes back online, it'll start syncing from its old height.
-
nikg83[m]
Can we make monerod pop random amount of blocks when restarting ? 5-100 blocks just to avoid finger printing
-
moneromooo
The "yes" was for you.
-
moneromooo
I made the wallet do that already. It doesn't actually pop, but requests blocks from an earlier quantized height.
-
nikg83[m]
moneromooo: When connecting to remote nodes ? Nice 👌
-
moneromooo
If you're good, you might still be able to guess the real height from timing though.
-
moneromooo
Can't recall whether done for untrusted only. That was a long time ago.
-
moneromooo
Back when I cared about leaks to third party nodes :/ Unintended consequences...
-
drflashd[m]
<moneromooo> "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
-
drflashd[m]
the node is standard latest github release bin for linux