Skip to content

Conversation

maflcko
Copy link
Member

@maflcko maflcko commented Oct 30, 2016

Follow up of #9016

@maflcko maflcko added the GUI label Oct 30, 2016
@jonasschnelli
Copy link
Contributor

Concept ACK. Will test soon.

@jonasschnelli
Copy link
Contributor

Any recommendation how to test this?

@maflcko
Copy link
Member Author

maflcko commented Oct 31, 2016

You could try to create a transaction which violates policy (e.g. a "free" transaction with full mempool or one which violates the ancestor/descendant limit)

src/qt/bitcoin-qt -testnet -limitancestorcount=1

@jonasschnelli
Copy link
Contributor

Tested ACK 3333e5a
bildschirmfoto 2016-11-01 um 08 31 52

@jonasschnelli jonasschnelli merged commit 3333e5a into bitcoin:master Nov 1, 2016
jonasschnelli added a commit that referenced this pull request Nov 1, 2016
3333e5a [qt] Return useful error message on ATMP failure (MarcoFalke)
@maflcko maflcko deleted the Mf1611-qtATMPerror branch November 1, 2016 09:35
@maflcko
Copy link
Member Author

maflcko commented Nov 1, 2016

(Strictly speaking, it should be impossible to test. Right now it can only be tested due to bugs such as #9019.)

@jonasschnelli
Copy link
Contributor

@MarcoFalke: you can test it (=run into such situation) in conjunction with CoinControl.

codablock pushed a commit to codablock/dash that referenced this pull request Jan 13, 2018
3333e5a [qt] Return useful error message on ATMP failure (MarcoFalke)
andvgal pushed a commit to energicryptocurrency/gen2-energi that referenced this pull request Jan 6, 2019
3333e5a [qt] Return useful error message on ATMP failure (MarcoFalke)
CryptoCentric pushed a commit to absolute-community/absolute that referenced this pull request Feb 15, 2019
3333e5a [qt] Return useful error message on ATMP failure (MarcoFalke)
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants