Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] master from stellar:master #381

Open
wants to merge 1,341 commits into
base: master
Choose a base branch
from
Open

Conversation

pull[bot]
Copy link

@pull pull bot commented Jun 7, 2021

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Jun 7, 2021
tamirms and others added 29 commits March 5, 2024 07:36
…e `ArchivePool` (#5224)

* Perform round robin w/ individual backoff
* Remove transient retry test from checkpoints
* go.mod fixups with a tidy run
…tatement / transaction timeout configured in postgres (#5223)
…pactor to reduce memory bloat during ingestion (#5252)
…5231)

* Add deprecation warning and test

* Update services/horizon/internal/flags.go

Co-authored-by: shawn <[email protected]>

* Update parameters_test.go

* Change the printed message

---------

Co-authored-by: shawn <[email protected]>
amishas157 and others added 30 commits December 2, 2024 17:15
This squash commit is the sum total of all the commits for this github issue - #5535

TL;dr 
Extend the ingest.Change struct to include information about the reason for the state change in the ledgerEntry.

* Include operation information in the Change struct

* Dont error out when operation index out of range

* Fix failing unit test

* Reafactor ledger_transaction.GetChanges() to use internal functions

* reformat comments

* Add all types of change reasons to the Change struct. Simplify LedgerTransaction.GetChanges()

* Add LCM and transaction info altogether in change entry

* Wrte help doc for Change Entry

* Add TxHash to LedgerTransaction struct

* reorg comments

* Comments cleanup

* Address PR review changes

* rename fields

* uncommit half baked changes

* Add helpers in intergration tests for creating captive core config

* fix updates to change struct

* Updates to integration.go

* Integration tests for change - part 1

* Undo all changes to parameters_test.go

* Make updates to comments and rename variables

* - Several changes to integration.go to pull out common functions from parameters_test.go to configure captive core
- Add flags to capture state for upgrade version in test.
- Add support to skip container deletion for debugging

- Add test for upgrade related changes

* cosmetic doc style changes

* check err before file close

* Add tx test and in change_test.go

* code cleanup

* Rework test fixtures

* reformat file

* Fix breaking test

* Address code review comments
…lient

Add General purpose API wrapper util
Bumps the go_modules group with 2 updates: gopkg.in/square/go-jose.v2 and [golang.org/x/crypto](https://github.com/golang/crypto).


Updates `gopkg.in/square/go-jose.v2` from 2.4.1 to 2.6.0

Updates `golang.org/x/crypto` from 0.24.0 to 0.31.0
- [Commits](golang/crypto@v0.24.0...v0.31.0)

---
updated-dependencies:
- dependency-name: gopkg.in/square/go-jose.v2
  dependency-type: direct:production
  dependency-group: go_modules
- dependency-name: golang.org/x/crypto
  dependency-type: indirect
  dependency-group: go_modules
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ueues the last batch of ledgers (LCM) within the specified range (#5563)

* ingest/ledgerbackend: fix to ensure that the ledger buffer properly queues the last batch of ledgers (LCM) within the specified range, preventing get_ledger from blocking indefinitely.

* Update Changelog
* Ignore generated checksums file

* Commit protos, generated code, helper code, and Makefile target

* go mod tidy

* Change address proto to be an enum + strkey representation of address

* Update location of proto files from protos/ to protos/ingest to be consistent with where the generated code should appear

This also helps simply the Makefile target
Right now, yes, the protos that we need to work on need to be put in the
/ingest path.
Tomorrow, we may need to have generated go files in some other path for some other source code.
At that time, redoing protos might be hard.

* Add README.md

* remove address helper

* Add unit tests for ser-deser of Asset proto

* newline

* Test cases for token transfer event

* Rework test fixture

* variable names
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.