Ripple API

[nelisky]

Yes, I did. Had I not done it there would be an error 'No such ledger'.

I don't think account_tx will ever give you "no such ledger". You can query for transactions from ledger zero to ledger one million and it will give you the latest 200. (Arguably, it probably should tell you which ledgers it has in the reply, but you can always check, it's published to the "server" stream.)

Oh, but it does, at least if you do "account_tx account ledger" for a specific ledger id (as opposed to a range).

Still haven't had a chance to try this over a better machine but I'll report on that once I get it done.

[1714857696]

1714857696

[1714857696]

1714857696

[1714857696]

1714857696

[1714857696]

1714857696

[JoelKatz]

Oh, but it does, at least if you do "account_tx account ledger" for a specific ledger id (as opposed to a range).

You're correct. It's kind of a quirk in the code. If you specify a ledger range, special code for ranges of ledgers handles it. If you specify one specific ledger, generic code that fails if the ledger isn't available handles it.

[nelisky]

Tried on a new, much better system, same difference. Opened an issue with the command outputs and config file.

[nelisky]

Oh, but it does, at least if you do "account_tx account ledger" for a specific ledger id (as opposed to a range).

You're correct. It's kind of a quirk in the code. If you specify a ledger range, special code for ranges of ledgers handles it. If you specify one specific ledger, generic code that fails if the ledger isn't available handles it.

@JoelKatz with the db fix mentioned in the issue I opened everything works great, thank you!

To infinity and beyond!

Now, a small doubt on workflow; I submit a payment for which no trust line exists, I assume this transaction never gets submitted to a ledger, right? At least I could not find my test one. The issue I'm having is one of atomicity, where I submit a tx and note the request ID to match the response, but say between send and response my ws dies, and don't get this response at all.

Can I poll for it afterwards? Or is the assumption that if I don't see it in a ledger for a set period of time I can just resubmit the request? The latter feels dangerous if the network is busy and lags a bit.

[ahbritto]

Now, a small doubt on workflow; I submit a payment for which no trust line exists, I assume this transaction never gets submitted to a ledger, right? At least I could not find my test one. The issue I'm having is one of atomicity, where I submit a tx and note the request ID to match the response, but say between send and response my ws dies, and don't get this response at all.

Can I poll for it afterwards? Or is the assumption that if I don't see it in a ledger for a set period of time I can just resubmit the request? The latter feels dangerous if the network is busy and lags a bit.

If a transaction could possibly apply, it is forwarded to the rest of the network. If a trust line doesn't exist, that won't stop a transaction from propagating because another transaction could create the line.

Take a look at this: https://ripple.com/wiki/Robustly_submitting_a_transaction

This describes how to submit transactions in an idempotent way. Generally, you want to build and store your transactions before you send them. Then you can send them as many times as you want. If you are coming back after a power failure, you could look for transactions that have been applied to your account since a specific ledger.

[nelisky]

Now, a small doubt on workflow; I submit a payment for which no trust line exists, I assume this transaction never gets submitted to a ledger, right? At least I could not find my test one. The issue I'm having is one of atomicity, where I submit a tx and note the request ID to match the response, but say between send and response my ws dies, and don't get this response at all.

Can I poll for it afterwards? Or is the assumption that if I don't see it in a ledger for a set period of time I can just resubmit the request? The latter feels dangerous if the network is busy and lags a bit.

If a transaction could possibly apply, it is forwarded to the rest of the network. If a trust line doesn't exist, that won't stop a transaction from propagating because another transaction could create the line.

Take a look at this: https://ripple.com/wiki/Robustly_submitting_a_transaction

This describes how to submit transactions in an idempotent way. Generally, you want to build and store your transactions before you send them. Then you can send them as many times as you want. If you are coming back after a power failure, you could look for transactions that have been applied to your account since a specific ledger.

Of course, I knew that from my first read of the documentation... thank you for pointing out just how spread I am