<n​ot_a_money_printer:matrix.org> It FCMP a quantum proof solution?

<n​ot_a_money_printer:matrix.org> Is FCMP a quantum proof solution?

<w​oodser:monero.social> vtnerd `status` shows 1(out)+1(in) connections

<w​oodser:monero.social> I isolated the last problem I'm seeing to 13ff355c, "Set response limits on http server connections": monero-project/monero 13ff355

<w​oodser:monero.social> vtnerd:

<s​yntheticbird:monero.social> wtf

<o​frnxmr:xmr.mx> This should only effect rpc 👀 uhoh(?)

abstract_tcp_server2 is also used in p2p

<v​tnerd:monero.social> woodser: the tx relaying issues were narrowed down to that patch?

<v​tnerd:monero.social> @woodser sorry not on irc

vtnerd: please open 9820 against release

<w​oodser:monero.social> vtnerd yes, with that patch, txs aren't being confirmed for some reason

woodser: fail to confirm meaning it prints "Unable to send transaction(s) via Dandelion++ stem" ?

<w​oodser:monero.social> no that only prints if I don't set the `--max-connections-per-ip` flag on 0cd7456

ok, is there any error message with 13ff355c?

<w​oodser:monero.social> nope

<v​tnerd:monero.social> woodser: I don't understand. I thought you narrowed the issue down to 13ff355c? Or is this situation that with 0cd7456 and 13ff355c txes don't relay, but only 0cd7456 prints an error?

<w​oodser:monero.social> building 0cd7456 will print an error produce test failures unless `--max-connections-per-ip` flag is used

<w​oodser:monero.social> but then there's a different error with 13ff355c, with or without `--max-connections-per-ip`

<w​oodser:monero.social> 0cd7456 will print an error *and fails my tests unless `--max-connections-per-ip` flag is used

<w​oodser:monero.social> both problems appear related to txs not confirming

<v​tnerd:monero.social> What is the error that 13ff355c prints?

<o​frnxmr:xmr.mx> vtnerd ^

<w​oodser:monero.social> no errors are printed, the tx is not confirmed according to the wallet

<v​tnerd:monero.social> The functional tests for this still work, and appear similar to your haveno test setup, so I don't even have a guess right now

<w​oodser:monero.social> yeah I don't know what it is either, but there's definitely some difference in how the wallets / monerods are behaving with 13ff355c. I just checked again, getting test failures with 13ff355c, which otherwise pass without it

<o​frnxmr:xmr.mx> Do have logs from the tests?

<o​frnxmr:xmr.mx> Is it on a CI that can he looked it?

<o​frnxmr:xmr.mx> Be*

<w​oodser:monero.social> nope, no logs or CI, just a test failure which shows that a wallet does not observe the multisig deposit txs to be unlocked when expected:

<w​oodser:monero.social> ```

<w​oodser:monero.social> Expected: "DEPOSITS_UNLOCKED"

<w​oodser:monero.social> Received: "DEPOSITS_PUBLISHED"

<w​oodser:monero.social> ```

<w​oodser:monero.social> though some of the trades in the test are completing successfully, so it doesn't happen every time