Skip to content

Releases: stellar/go

Horizon v2.8.0

23 Aug 17:41
57979d4
Compare
Choose a tag to compare

Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.

In the 2.9.0 Horizon release, the --ingest flag will be set to true by default.

  • Limit reap to 100k ledgers/second, to prevent excess CPU usage (3823).
  • Improve performance of path finding endpoints (3818).

Horizon v2.7.0

02 Aug 18:05
4228fac
Compare
Choose a tag to compare

Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.

In the upcoming 2.9.0 Horizon release, the --ingest flag will be set to true by default. Please update your deployment scripts before this.

  • If --captive-core-config-path is not set, the config file is generated based on network passhprase. (3783)
  • Fix bug in horizon reap system (used by horizon db reap command and when horizon is configured with --history-retention-count) which could lead to partial deletions. (3754)
  • Log debug messages from captive core at the appropriate log level. (3746)
  • Add a feature flag --captive-core-reuse-storage-path/CAPTIVE_CORE_REUSE_STORAGE_PATH that will reuse Captive Core's storage path for bucket files when applicable for better performance. (3750)

Horizon v2.6.1

12 Jul 16:14
71350e6
Compare
Choose a tag to compare

Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.

  • Fix bug introduced in v2.6.0 (#3737), preventing usage of horizon db migrate up/down/redo commands. (#3762)

Horizon v2.6.0

12 Jul 13:03
8107a7c
Compare
Choose a tag to compare

Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.

  • Precompute trade aggregations during ingestion to improve performance. Will rebuild the aggregations as part of the database migrations. (3641 & 3760).
  • Require COUNT param when running horizon db migrate down COUNT to prevent accidentally running all downwards migrations. Add horizon db migrate status command. (#3737)
  • Fix a bug in fee_account_muxed and fee_account_muxed_id fields (the fields were incorrectly populated with the source account details). (3735)
  • Validate ledger range when calling horizon db reingest range so that we respond with an error when attempting to ingest ledgers which are not available in the history archives. (3738)
  • Improve performance of transaction submission. (3563)

horizonclient v7.1.1 & txnbuild v7.1.1

25 Jun 19:58
2601c84
Compare
Choose a tag to compare

horizonclient

  • Added transaction and operation result codes to the horizonclient.Error string for easy glancing at string only errors for underlying cause.
  • Fix bug in the transaction submission where requests with large transaction payloads fail with an HTTP 414 URI Too Long error (#3643).
  • Fix a data race in Client.fixHorizonURL(#3690).
  • Fix bug which occurs when parsing operations involving muxed accounts (#3722).

txnbuild

Bug Fixes

  • Claimable balance IDs are now precomputed correctly (Transaction.ClaimableBalanceID(int)) even when the transaction's source account is a fully-muxed account (#3678).
  • Fix muxed account address parsing for account merge operation (#3722).

Horizon v2.5.2

25 Jun 13:13
739936f
Compare
Choose a tag to compare

Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which can take up to 20 minutes), Horizon will not ingest new ledgers.

  • Fix a bug in the method unmarshaling payment operation details. (#3722)

Horizon v2.5.1

23 Jun 18:56
ccdcbcb
Compare
Choose a tag to compare

Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which can take up to 20 minutes), Horizon will not ingest new ledgers.

  • Fix for Stellar-Core 17.1.0 bug that can potentially corrupt Captive-Core storage dir. (#3715)
  • All muxed ID fields are now represented as strings. This is to support JS that may not handle uint64 values in JSON responses properly. (#3716)

Horizon v2.5.0

22 Jun 13:52
62f568f
Compare
Choose a tag to compare

Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which can take up to 20 minutes), Horizon will not ingest new ledgers.

  • Add new command horizon db detect-gaps, which detects ingestion gaps in the database. The command prints out the db reingest commands to run in order to fill the gaps found (3672).
  • Performance improvement: Captive Core now reuses bucket files whenever it finds existing ones in the corresponding --captive-core-storage-path (introduced in v2.1.0 rather than generating a one-time temporary sub-directory (3670). This feature requires Stellar-Core version 17.1 or later.
  • Horizon now monitors the Stellar Core binary on disk (pointed to by --stellar-core-binary-path/STELLAR_CORE_BINARY_PATH) and restarts its Captive Core subprocess if it detects changes (i.e a more recent file timestamp for the Stellar Core binary) (3687).
  • POST /transactions return 503 Service Unavailable instead of 504 Gateway Timeout if connected Stellar-Core is out of sync (3653).
  • Add protocol version metrics: horizon_ingest_max_supported_protocol_version, horizon_ingest_captive_stellar_core_supported_protocol_version, horizon_stellar_core_supported_protocol_version (3634).
  • Fixed crash in horizon ingest verify-range command (3682).
  • Handle replica conflict errors gracefully (3674).
  • Fix data race in request parameters handling (3690).
  • Fix bug where the configuration for CAPTIVE_CORE_LOG_PATH, CAPTIVE_CORE_PEER_PORT, and CAPTIVE_CORE_HTTP_PORT were ignored if they were configured via environment variables instead of command line arguments. (3702).
  • Error when setting BUCKET_DIR_PATH through --captive-core-config-path (3707).

Horizon v2.4.1

09 Jun 13:43
Compare
Choose a tag to compare

Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which can take up to 20 minutes), Horizon will not ingest new ledgers.

Code Changes

  • Fix bug in horizon db reingest range command, which would throw a duplicate entry conflict error from the DB. (3661).
  • Fix bug in DB metrics preventing Horizon from starting when read-only replica middleware is enabled. (3668).
  • Fix bug in the value of route in the logs for rate-limited requests (previously it was set to undefined). (3658).

horizonclient v7.1.0 & txnbuild v7.1.0

01 Jun 17:15
163fc5c
Compare
Choose a tag to compare

horizonclient

  • Added transaction and operation result codes to the horizonclient.Error string for easy glancing at string only errors for underlying cause.
  • Fix bug in the transaction submission where requests with large transaction payloads fail with an HTTP 414 URI Too Long error (#3643).

txnbuild

New features

  • Add SequenceNumber function to Transaction.
  • Add AddSignatureDecorated function to Transaction.

Bug Fix

  • BaseFee in TransactionParams when calling NewTransaction is allowed to be zero because the fee can be paid by wrapping a Transaction in a FeeBumpTransaction. (#3622)