moneromooo, Now there are a lot of tx when i do print_pool_sh, looks like those are all the tx in the network still need to get confirmed?

Yes.

Any way i can force this pending tx to get failed status so i know it will not try to push this tx again and again?

Does it show pending or failed in monero-wallet-cli ?

In GUI it shows pending. I´ll check CLI

moneromooo, In CLI it shows as failed.

Possible that the GUI can’t display failed transactions.

So i assume its safe to re-send the transaction.

any way to simulate a failed transaction?

No idea.

If I manage to simulate a failed tx I can add GUI support for it :P

For a failed tx: start the daemon with --offline, send one, then flush_txpool_, then let the wallet refresh a couple time.

moneromooo: E: failed to get output distribution, request = Daemon reports suspicious number of rct outputs

when trying to send with --offline

ok managed to do it

Do you know why then ?

yep my daemon was like 1 day behind

so I synced up and restarted with --offline

now I have the problem that is_failed always evaluates to true

does ^ look correct?

Failed it set if the tx was not seen in the chain nor the pool for two refreshes.

Does it work in monero-wallet-cli ?

yes

I assume you copied the logic off monero-wallet-cli ?

the logic did already exist

the one I linked before

Then the most likely seems that the refresh calls are wrong.

Was that particular tx mined ?

nope

directly after sending both pending and failed are both true in wallet2_api

(without getting mined yet)

And it's in the txpool ?

yes

I can see it on xmrchain.net

Then you possibly refreshed the chain but not the txpool, so as far as it's concerned, it sees it in neither.

Bump log level in monerod to see which RPC are being called.

*rpc*:DEBUG ought to do

interesting

using my local node it works

but my remote node (restricted) does not

I tested CLI with my local node

Ah, maybe restricted mode hides the tx.

(If received by RPC rather than P2P)

Yes, it must do. You wouldn't want people to see what you send.

CLI correctly sets it to false even when using a restricted remote node

s/false/failed/

You said it was always setting to failed, so maybe it's accidentially setting it correctly.

will test once my balance is unlocked

`pending out`

looks good

in CLI

oh well will maybe ask xiphon to take a look at it, starting to get confused

if I create the tx with the GUI + restricted node -> open same wallet in CLI it will say failed while still pending

if I do the same in CLI + restricted node it will say correctly pending

guess that’s the problem

The GUI probably set it wrong before the wallet has a chance to do anything.

with local node everything is ok in both CLI / GUI

here is_failed doesn’t even get set

so maybe it defaults to true?

No idea without looking.

I looked. Looks like pending when created.

yep the pending flag is correct

the failed one is just the problem

Flag ? It's an enum. It's one or the other.

(or the third)

on the GUI side it’s a flag

see line 207

OK, I see it, but it's initialized from the enum AFAICT.

yes