Horizon 1.5.0 support
abuiles opened this issue · comments
Adolfo Builes commented
Horizon 1.5.0 added a new field to the ledgers resource called tx_set_operation_count
, if your SDK has support for /ledgers
or ledger
resources, then it should include this new field. The value can be a number
or null
.
This value represents the total number of operations in the transactions set. You can use it to find out if recent ledgers have been full (and therefore subject to surge pricing) or not.
Are you curious about other changes in Horizon?
My two picks are:
- The removal of
--ingest-failed-transactions
flag, which means from now on Horizon will always ingest failed transactions. If you run your own Horizon, this might have an impact on your database. - A new experimental mode of doing database reingestion which uses a Stellar Core subprocess instead of a persistent Stellar Core database. Please give this a try and let us know if you find any issue!
You can see the full changelog in the release notes https://github.com/stellar/go/releases/tag/horizon-v1.5.0
Jem Mawson commented
Thanks Adolfo. Can someone at SDF please update
https://hub.docker.com/r/stellar/quickstart latest to 1.5.0?
…On Thu, 2 Jul 2020 at 07:33, Adolfo Builes ***@***.***> wrote:
Horizon 1.5.0 <https://github.com/stellar/go/releases/tag/horizon-v1.5.0>
added a new field to the ledgers resource called tx_set_operation_count,
if your SDK has support for /ledgers or ledger resources, then it should
include this new field. The value can be a number or null.
This value represents the total number of operations in the transactions
set. You can use it to find out if recent ledgers have been full (and
therefore subject to surge pricing) or not.
Are you curious about other changes in Horizon?
My two picks are:
1. The removal of --ingest-failed-transactions flag, which means from
now on Horizon will always ingest failed transactions. If you run your own
Horizon, this might have an impact on your database.
2. A new experimental mode of doing database reingestion which uses a
Stellar Core subprocess instead of a persistent Stellar Core database.
Please give this a try and let us know if you find any issue!
You can see the full changelog in the release notes
https://github.com/stellar/go/releases/tag/horizon-v1.5.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#302>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAFKYZL4Y56FQDZO3VAUULRZOTTXANCNFSM4OOCFYZA>
.
Adolfo Builes commented
Sorry, I missed this message. We'll look into it.
--
Adolfo Builes
…On Wed, Jul 1, 2020 at 5:07 PM Jem Mawson ***@***.***> wrote:
Thanks Adolfo. Can someone at SDF please update
https://hub.docker.com/r/stellar/quickstart latest to 1.5.0?
On Thu, 2 Jul 2020 at 07:33, Adolfo Builes ***@***.***>
wrote:
> Horizon 1.5.0 <https://github.com/stellar/go/releases/tag/horizon-v1.5.0
>
> added a new field to the ledgers resource called tx_set_operation_count,
> if your SDK has support for /ledgers or ledger resources, then it should
> include this new field. The value can be a number or null.
>
> This value represents the total number of operations in the transactions
> set. You can use it to find out if recent ledgers have been full (and
> therefore subject to surge pricing) or not.
> Are you curious about other changes in Horizon?
>
> My two picks are:
>
> 1. The removal of --ingest-failed-transactions flag, which means from
> now on Horizon will always ingest failed transactions. If you run your
own
> Horizon, this might have an impact on your database.
> 2. A new experimental mode of doing database reingestion which uses a
> Stellar Core subprocess instead of a persistent Stellar Core database.
> Please give this a try and let us know if you find any issue!
>
> You can see the full changelog in the release notes
> https://github.com/stellar/go/releases/tag/horizon-v1.5.0
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#302>, or
unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAAFKYZL4Y56FQDZO3VAUULRZOTTXANCNFSM4OOCFYZA
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#302 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAFKDBODXNZPSNI2GZT7QTRZOXQTANCNFSM4OOCFYZA>
.
Jem Mawson commented
Confirmed working. Thanks!