-
xmr-pr
moneromooo-monero opened pull request #6877: p2p: add --max-connections-per-ip daemon option
-
xmr-pr
-
dEBRUYNE
Would it be worthwhile to put a reminder on the mailing list regarding the upcoming scheduled network upgrade?
-
Tonuy
Hi guys!
-
Tonuy
Is exist guide for running python tests in monero project?
-
Tonuy
got "Unresolved reference 'framework'" when i'm trying to run monero/tests/functional_tests/sign_message.py
-
Tonuy
How to fix this error and execute tests?
-
Tonuy
pls help!!!
-
ErCiccione[m
dEBRUYNE: I think it woulds. We are less than a week away from the hf
-
moneromooo
How are you running it ?
-
moneromooo
dEBRUYNE: maybe wait till selsta's released again, there's one very soon AIUI.
-
moneromooo
Anyway, tests: make release-test
-
dEBRUYNE
ErCiccione[m: All right. As a side note, I updated the pruning guide on the Monero SE
-
dEBRUYNE
moneromooo: Yeah I think tomorrow or tuesday
-
dEBRUYNE
Will write up a draft in any case, then we can push it to the mailing list shortly after the release
-
ErCiccione[m
Cool. Thanks for that dEBRUYNE
-
ErCiccione[m
Yeah if there is a point release coming, better wait
-
dEBRUYNE
I do think someone mentioned that blocks recently have been mined faster than average
-
dEBRUYNE
Which basically brought forward the hf date by a bit
-
NHnCH3
what does mean "Next needed pruning seed: 4" by sync_info ? I didn't pruning...
-
moneromooo
It's the pruning slot the next needed block falls in.
-
moneromooo
This doesn't depend on whether you prune or not, it's deterministic based on height.
-
yrd
-
moneromooo
Kinda pisses me off they'd just do that without LD_LIBRARY_PATH.
-
moneromooo
It's really a problem with ld.so.
-
moneromooo
Or whatever looks anywhere that's not system and not in LD_LIBRARY_PATH.
-
kpcyrd
there's $ORIGIN to do this in a safer way, but the release tar ball doesn't contain any libs anyway
-
moneromooo
Hmm. Never heard of that var. I'll look it up, thanks.
-
moneromooo
It's unlookupable :D
-
kpcyrd
`rpath $origin` is what you want to google for :)
-
moneromooo
ty
-
kpcyrd
but you should be able to just drop the rpath all together, on my system all libs are loaded from /usr/lib or /usr/lib64 anyway
-
moneromooo
Looks like this is enough: set(CMAKE_SKIP_RPATH ON)
-
moneromooo
(tested on daemon)
-
moneromooo
I'm on a static build though.
-
hyc
on that note, the CLI builds have an embedded rpath too
-
hyc
RUNPATH /home/ubuntu/build/monero/contrib/depends/x86_64-linux-gnu/lib:
-
hyc
I noticed it while working on $6862
-
kpcyrd
hyc: which binary is that?
-
hyc
all of them
-
hyc
in the reproducible CLI builds
-
hyc
it's been like that for probably all of the reproducible releases
-
hyc
moneromooo: in case you're interested, I've revamped the crypto API in LMDB
git.openldap.org/openldap/openldap/-/tree/mdb.master3
-
hyc
still not sure howe we get from here to there since the DB format is incompatible with LMDB 0.9
-
kpcyrd
hyc: the binaries currently in arch linux are fine, the daemon is on 0.17.0.1 and the gui is still on 0.16.0.3 because the update got flagged
-
hyc
easiest is to use mdb_dump in 0.9 and mdb_load in 1.0
-
hyc
kpcyrd: I guess arch isn't using gitian for reproducible builds then
-
moneromooo
OK. The conversion problem would not apply since the wallet does not use LMDB atm.
-
hyc
yes but we would have 2 different versions of LMDB library
-
hyc
if we don't convert the daemon+blockchain
-
moneromooo
Oh. Even if we don't use crypto, it changes ?
-
hyc
yes
-
hyc
I mean, the crypto feature is built on LMDB 1.0
-
hyc
I had originally written it on LMDB 0.9, but it's been tweaked since then
-
moneromooo
OK.
-
hyc
I suppose I could try to backport it onto 0.9 again
-
moneromooo
Well, we'd first need someone willing to tackle a LMDB wallet.
-
hyc
true
-
kpcyrd
-
hyc
probably something flaky in our contrib/depends/toolchain.cmake
-
hyc
hm, setting SET(CMAKE_SKIP_RPATH ON) in the toolchain file doesn't work
-
hyc
cmake is still seeing CMAKE_SKIP_RPATH OFF, and emitting an rpath
-
moneromooo
I put it in CMakeLists.txt, right before set(CMAKE_C_FLAGS_RELEASE "-DNDEBUG ${OPT_FLAGS_RELEASE}")
-
hyc
still no joy
-
hyc
always get this
-
hyc
CMAKE_SKIP_RPATH:BOOL=NO
-
hyc
in CMakeCache.txt
-
hyc
wtf.... it just doesn't want to obey that setting
-
hyc
ok it takes it if I put -DCMAKE_SKIP_RPATH=ON on the cmake command line
-
hyc
btw what version of cmake did you use?
-
hyc
gitian build uses 3.10.2
-
hyc
my regular build env uses 3.13.4
-
hyc
and that setting definitely removed the rpath from the resulting monerod, good
-
hyc
now the question is why I can't turn it off with CMakeLists.txt or the toolchain file
-
UkoeHB_
doesn't cmake ignore stuff in the CMakeLists.txt file if there is already a CMakeCache.txt file? maybe delete the cache file and rerun cmake
-
hyc
I deleted everything before each run
-
hyc
rm -rf *
-
hyc
same result. the only way that worked was -D on the cmdline
-
Inge-
I still got a tx as a red "failed" with monero-wallet-cli using --trusted-daemon on 0.17.0.1 with a 0.17.0.1 node.
-
selsta
initially failed?
-
selsta
did you connect to an unrestricted node?
-
xmr-pr
muff1nman opened issue #6878: Cannot use `show_transfers in` without being connected to daemon
-
xmr-pr
-
Inge-
selsta: my own node
-
selsta
Inge-: is your node restricted rpc?
-
Inge-
yes --restricted-rpc
-
selsta
and what is the exact problem?
-
Inge-
that a sent tx displays as a red failed
-
Inge-
but then at some point it gets sent anyway. The going theory was that I had not added --trusted-daemon the first times I saw it, and that it is related to D++
-
Inge-
but now I've seen it with --trusted-daemon
-
selsta
Inge-: no, the theory is that your node is restricted
-
selsta
maybe I mistyped last time
-
selsta
can you try unrestricted node (with rpc login)
-
selsta
the issue is that the mempool is hidden in d++ stem phase (or so) so the client does not know the status of the transaction, so it gets shown as failed
-
selsta
with unrestricted node your client sees the mempool
-
Inge-
I will test that out. But this is going to be a common error for remote node users in 0.17.1 then?
-
selsta
vtnerd suggested multiple ways to fix this