Merge p23 into master #5783
Open
Merge p23 into master #5783
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* xdr: Update XDR definitions for Protocol 23
…ol 23 (#5587) --------- Co-authored-by: George <[email protected]> Co-authored-by: tamirms <[email protected]>
…alance() restore case (#5616)
…representation of evictions (#5619)
* Remove stellar core running in in-memory mode. Also, remove the config parameter from the Horizon config, ingest library captive core config and any related code. * Update integration tests * Update Changelog
Merge master into protocol-23 branch
Conflicts: .github/workflows/galexie-release.yml .github/workflows/galexie.yml .github/workflows/horizon.yml services/horizon/internal/ingest/processor_runner_test.go services/horizon/internal/ingest/processors/stats_change_processor_test.go services/horizon/internal/ingest/verify_test.go
) * Update fields to coincide with stellar/stellar-core#4721
…-21/merge-master-into-p23 Conflicts: .github/workflows/horizon.yml
… ot the latest core rc p23 build
…into-p23 Merge `master` into `protocol-23` feature branch
* initial commit for sac event parsing * break out code for parsing SAC v3 and v4 * Add unit tests for all stellar asset contract parsing * Update horizon processors code and unit tests to read from the new horizon/internal/support/contractevents package * Initial change to separate V3 events into their own function * Rework the receiver function GetDiagnosticEvents on TransactionMeta to NOT return an error * Rework diagnostic events completely. WIll fix failing tests later * Unit tests for the new events functions * Fix unit test fixtures to account for changes in getXXXEvents functionality in horizon and processors/ * make destinationMemo public * Address code review comments
#5715) * Make provision to add destination_muxed_id in the output for the operations endpoint. This is partial work. As in, this commit helps to ensure that downstream cli can be made aware of it. The actual work to ensure that destination_muxed_id is parsed from StellarAssetContract and stored in DB as a part of parsing details will be done separately * update changelog for horizon * address code review comments
…perations endpoint (#5739) * Add support for muxed information from contractEvents to show up in operations endpoint * Replace mint with transfer in integration test for SAC with muxed info * Make the code work for the sac test * Remove extra comment * address code review comments * address code review comments * address code review comments * remove unnecssary use of QuickExpiration * MuxedId can only ever be uint64 in SAC events --------- Co-authored-by: tamirms <[email protected]>
services/horizon: Port master back to protocol-23, pull in the verify-range update
* Add logic for muxed info in effects processor * address code review comments
…regations timestamp with btree (#5745)
Merge master into protocol-23
…he protocol verison (#5768)
#5738) * Include muxed info for the case where sender and receiver are both the same and the issuer of the asset in a classic operation * Do not include muxed information in events from smart contract transctions that are pre protocol 23 * Make sure that the test fixture inputs are immutable * undo changes to ledger transaction * undo changes to token transfer helpers * Add unit tests * Add unit test for wierd transfer case where src = dest = asset isser * Fix typo
… check for compatibility with SKIP_TXMETA (#5776)
* Horizon changelog * Horizon changelog
.github/workflows/galexie-release.yml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mega merge PR to merge p23 into master for the go monorepo