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

soroban-rpc: Pull in Recent Soroban RPC changes from soroban-tools #54

Closed
wants to merge 5 commits into from

Conversation

stellarsaur
Copy link
Contributor

What

Related to CLI/RPC repo split.

This PR pulls in all merged PRs from soroban-tools repo after this PR.

Why

All new contributions to RPC should live in soroban-rpc. However, for soroban-tools work that was already in progress during the initial repo migration, we should pull RPC related changes into this repo.

2opremio and others added 5 commits February 5, 2024 14:42
1. Get rid of the in-memory operation index (since it was always set to zero anyways)
2. Keep events serialized while in memory (it saves quite a bit of space due to the inneficient representation of unions in golang).

(cherry picked from commit 433cd44)
* Remove panic - 1

* Remove panic - 2

* Remove panic - 3

* Remove panic - 4

* Small changes - 1

* undo changes in Get() func

* undo changes - 2

* undo changes - 3

* add test for append error

(cherry picked from commit b6671e2)
* Remove panic - 1

* Remove panic - 2

* Remove panic - 3

* Remove panic - 4

* Small changes - 1

* undo changes in Get() func

* undo changes - 2

* undo changes - 3

* add test for append error

(cherry picked from commit b6671e2)
* Bump dependencies for pubnet release

* Fix core version checker to accept rc version tags

(cherry picked from commit 90f7cd9)
@stellarsaur
Copy link
Contributor Author

Closing this to re-do with correct ordering of PRs

@stellarsaur stellarsaur closed this Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants