Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with selected inputs for the send transaction #113

Open
dexX7 opened this issue Oct 2, 2015 · 0 comments
Open

Error with selected inputs for the send transaction #113

dexX7 opened this issue Oct 2, 2015 · 0 comments

Comments

@dexX7
Copy link
Member

dexX7 commented Oct 2, 2015

From time to time regtests fail due to the transaction input selection. I noticed it for the following test more than once (but rarely):

  • "Historical STO transactions are not affected by reorganizations"
foundation.omni.test.rpc.reorgs.SendToOwnersReorgSpec
    After invalidating a send to owners transaction, the transaction is invalid
    After invalidating a send to owners transaction, the original balances are restored
    Historical STO transactions are not affected by reorganizations

Historical STO transactions are not affected by reorganizations FAILED
    com.msgilligan.bitcoinj.rpc.JsonRPCStatusException: Error with selected inputs for the send transaction
        at com.msgilligan.bitcoinj.rpc.RPCClient.handleBadResponseCode(RPCClient.java:137)
        at com.msgilligan.bitcoinj.rpc.RPCClient.send(RPCClient.java:106)
        at com.msgilligan.bitcoinj.rpc.RPCClient.send(RPCClient.java:154)
        at com.msgilligan.bitcoinj.rpc.RPCClient.send(RPCClient.java:177)
        at foundation.omni.rpc.OmniClient.omniSendSTO(OmniClient.java:339)
        at foundation.omni.test.rpc.reorgs.SendToOwnersReorgSpec.Historical STO transactions are not affected by reorganizations(SendToOwnersReorgSpec.groovy:167)

Related line: foundation/omni/test/rpc/reorgs/SendToOwnersReorgSpec.groovy#L167

It's not clear to me why exactly. The underlying issue is that the sender has not enough BTC, when trying to send the transaction.

This might be caused, because there is a transaction inbetween with high fees (i.e. many inputs), but I can't really reproduce it in a controlled manner.

Let's keep an eye on it though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant