Releases: stellar/go
Releases · stellar/go
Horizon v0.14.1
This release contains several bug fixes:
- Assets stats can cause high CPU usage on stellar-core DB. If this slows down the database it's now possible to turn off this feature by setting
DISABLE_ASSET_STATS
feature flag. This can be set as environment variable (DISABLE_ASSET_STATS=true
) or CLI parameter (--disable-asset-stats=true
). - Sometimes
/accounts/{id}/offers
returns500 Internal Server Error
response when ledger data is not available yet (for new ledgers) or no longer available (CATCHUP_RECENT
deployments). It's possible to setALLOW_EMPTY_LEDGER_DATA_RESPONSES
feature flag as environment variable (ALLOW_EMPTY_LEDGER_DATA_RESPONSES=true
) or CLI parameter (--allow-empty-ledger-data-responses=true
). With the flag set totrue
"Offers for Account" endpoint will returnnull
inlast_modified_time
field when ledger data is not available, instead of500 Internal Server Error
error.
Bug fixes
- Feature flag to disable asset stats (#668).
- Feature flag to allow null ledger data in responses (#672).
- Fix empty memo field in JSON when memo_type is text (#635).
- Improved logging: some bad requests no longer generate
ERROR
level log entries (#654). /friendbot
endpoint is available only whenFriendbotURL
is set in the config.
Archivist v0.2.0
- Fixed duplicated data when reading an archive file (#374).
Horizon v0.14.0
Breaking changes
- Offer resource
last_modified
field removed (see Bug Fixes section). - Trade aggregations endpoint accepts only specific time ranges now (1/5/15 minutes, 1 hour, 1 day, 1 week).
- Horizon sends
Cache-Control: no-cache, no-store, max-age=0
HTTP header for all responses.
Deprecations
- Account > Signers collection
public_key
field is deprecated, replaced bykey
.
Changes
- Protocol V10 features:
- New
bump_sequence
operation (as in CAP-0001).- New
bump_sequence
operation. - New
sequence_bumped
effect. - Please check CAP-0001 for new error codes for transaction submission.
- New
- Offer liabilities (as in CAP-0003):
/accounts/{id}
resources contain new fields:buying_liabilities
andselling_liabilities
for each entry inbalances
.- Please check CAP-0003 for new error codes for transaction submission.
- New
- Added
source_amount
field topath_payment
operations. - Added
account_credited
andaccount_debited
effects forpath_payment
operations. - Friendbot link in Root endpoint is empty if not set in configuration.
- Improved
ingest
package logging. - Improved HTTP logging (
forwarded_ip
,route
fields,duration
is always in seconds). LOGGLY_HOST
env variable has been replaced withLOGGLY_TAG
and is adding a tag to every log event.- Dropped support for Go 1.8.
Bug fixes
- New fields in Offer resource:
last_modified_ledger
andlast_modified_time
, replace buggylast_modified
(#478). - Fixed pagination in Trades for account endpoint (#486).
- Fixed a synchronization issue in
ingest
package (#603). - Fixed Order Book resource links in Root endpoint.
- Fixed streaming in Offers for Account endpoint.
Horizon v0.13.3
Bug fixes
- Fixed large amounts rendering in
/assets
.
Horizon v0.14.0 rc3
Release Candidate. Do not use in production.
Horizon v0.13.2
Bug fixes
- Fixed a bug in
amount
andprice
packages triggering long calculations.
Horizon v0.14.0 rc2
Release Candidate. Do not use in production.
Horizon v0.14.0 rc1
Release Candidate. Do not use in production.
Horizon v0.13.1
Bug fixes
- Fixed a conversion bug when
timebounds.max_time
is set toINT64_MAX
.
Horizon v0.13.0
Breaking changes
amount
field in/assets
is now a String (to support Stellar amounts larger thanint64
).
Changes
- Effect resource contains a new
created_at
field. - Horizon responses are compressed.
- Ingestion errors have been improved.
horizon rebase
command was improved.
Bug fixes
- Horizon now returns
400 Bad Request
for negativecursor
values.
Upgrade notes
DB migrations add a new indexes on history_trades
. This is very large table so migration may take a long time (depending on your DB hardware). Please test the migrations execution time on the copy of your production DB first.