Conversation
* go/proxyd: Proxy requests as batched RPC We forward several RPC request objects to upstreams using the JSON-RPC batch functionality. This should be more efficient than serialized RPC request proxying the round-trip latency of the remaining request objects are eliminated. A new server config, `max_upstream_batch_size`, is introduced to limit the number of RPC request objects in a single batch request. This is to avoid overloading upstream as proxyd may accept a large number of request objects in a single request by having a large `max_body_size_bytes` config value. * remove flakes: no more SequencedResponseHandler Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Removes the Helper_SimpleProxy contract by replacing code that relies on it. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Cleans up tests for all Library contracts using same techniques as previous PRs. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* refactor: replace calls to getNetwork() with getChainId util * requested changes
- Adopts Go workspaces for future compatibility with the Bedrock move into the monorepo - Moves Go packages to the root of the repo in order to fix import paths - Rewrites existing Go import paths - Removes Stackman, since it's not needed anymore Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* feat: add go packages to package.json * feat: correct conf_remaining calculation Subtaction was being performed in the wrong order, causing underflow.
🦋 Changeset detectedLatest commit: 44c293d The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
github-actions
bot
added
2-reviewers
C-protocol-critical
theochap
pushed a commit
that referenced
this pull request
Dec 10, 2025
Defines `EntryNotFoundError` to replace `String` for error variant `StorageError::EntryNotFound`
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
No description provided.