Could it be that monero-wallet-rpc documentation is **outdated**? Can someone else confirm that they're seeing what I'm seeing?... (full message at libera.ems.host/_matrix/media/r0/do…b0a4b033581d1320f57c103529a160ce407)

It pretty much always is.

<moneromooo> "It pretty much always is." <- Is there something that can be done about this? Has anyone addressed this in the past?

Yes, update it and PR the change.

There is an open PR with the updates

it's still waiting for reviewers

^ this is more updated

Yes, but that's not addressing the underlying issue, though. The underlying issue is that keeping the code and the documentation in sync is difficult when it's done manually. I'm interested if someone has attempted to find the right tools to make this process automatic.

Not to my knowledge. Would be a good idea tho, since it's being very hard to get people to review the new documentation, so things stay outdated

There is no way to generate useful documentation automatically.

Good documentation tells you things like semantics, which cannot be inferred from code.

And documention that paraphrases variable names is useless.

Since when does ledger just support monero? If I'm not misremembering, i had to get the monero app from some GitHub or seperate site earlier this year.

I didn't mean to generate the documentation automatically as in take variable names and stuff them inside a table after a function name. No. In fact I think the current documentation is good. What I'm challenging is the way this documentation is being maintained because the current way requires keeping two... (full message at libera.ems.host/_matrix/media/r0/do…3c669e471e21a7379dca771fcfb3bf80fc9)

Of course you still have to actually write the documentation but it's all in one place and any discrepancies are easier to spot during code reviews.

<monerobull[m]> "Since when does ledger just..." <- It has supported it for years now. Just can't use Monero in the Ledger Live app (which you shouldn't use anyways). But the Ledger app has been available via Ledger Live for like 3y.

<selsta> "make -C build/release/ wallet_rp..." <- What's the target for just monerod?

Maybe: `make -C /monero/build/release/ daemon -j6 release-static-linux-x86_64`

Testing now.

Hmm, do I have to run make once before specifying the target, in order to create build files? Or is there some other way I can generate those build files?

selsta would love any input on this, should save me a ton of build time for my Docker images if I can get it sorted 😀

If I run make and then cancel it, and run again with the above flags it works -- but surely there's a better way I don't know

Seems that manually running the generated cmake command first works:... (full message at libera.ems.host/_matrix/media/r0/do…2eb0d6f6fb10bc164c34ce2172a689abedb)

* Seems that manually running the generated cmake command first works, i.e.:... (full message at libera.ems.host/_matrix/media/r0/do…196bec325b9e5426bfd74a6e620923474b2)

Hey guys, I've been directed here as I have a synching problem that the advice from Monero group didn't solve

Can I go ahead?

I know this is for Dev's only, that's why I ask

crowstick: Yes, please ask. It seem like it may be an edge case with Trezor.

Yesterday: My wallet stopped synching and I have XMR from 20 days ago on 3 / 10 confirmations and locked. Then there is XMR that I sent four days ago that never arrived. The wallet flicks from "starting the node" to "searching node" but never connects.

I have just re-installed the wallet but the same. I'm using a Trezor. Now: I left the wallet synching and went to bed. I got up about 2 am and checked it and it was jammed on a page saying confirm on Trezor. I had to restart the node. Then it happened again that morning. Tonight I have tried again and it lost connection and got stuck on starting node after a little progress. Now I went to close and it's running stuck on closing

wallet. Seems to be a problem here.

Yesterday I ran in advanced mode and changed the node to node.sethforprivacy.com and 18089. Restore height 2,000,000.

s/I have just re-installed the wallet but the same. I'm using a Trezor. Now: I left the wallet synching and went to bed. I got up about 2 am and checked it and it was jammed on a page saying confirm on Trezor. I had to restart the node. Then it happened again that morning. Tonight I have tried again and it lost connection and got stuck on starting node after a little progress. Now I went to close and it's running stuck on closing

wallet. Seems to be a problem here./I have just re-installed the wallet but the same. I'm using a Trezor. I was given advice to run in advanced mode and changed the node to node.sethforprivacy.com and 18089. Restore height 2,000,000. I left the wallet synching and went to bed. I got up about 2 am and checked it and it was jammed on a page saying confirm on Trezor. I had to restart the node. Then it happened again that morning.

Tonight I have tried again and it lost connection and got stuck on starting node after a little progress. Now I went to close and it's running stuck on closing wallet. Seems to be a problem here. /

It's now frozen on the Trezor

Is this a Trezor issue?

sethsimmons: yes it's daemon

<selsta> "Seth For Privacy: yes it's..." <- Thanks!

<crowstick[m]> "Is this a Trezor issue?" <- Is your Trezor fully up to date?

That step goes through quickly for me when syncing on a Trezor.

<sethsimmons> "Is your Trezor fully up to date?" <- Finally it completed. Then synch for a bit, then asked for my pin to update, after entering, as before, get's suck here:

Both frozen again

s/synch/synched/

crowstick[m]: did you install the latest trezor firmware?

I will check now

That was the problem, thanks, I updated the firmware, seems it was all the Trezor's problem. Thank you