-
Notifications
You must be signed in to change notification settings - Fork 87
Tracking PR for v0.13.0 release #1346
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
base: main
Are you sure you want to change the base?
Conversation
- Normalized response size limits to 4MB - Standardized naming in protobuf schema
This fixes an issue with the gRPC client builder where the content negotiation header was only set if the RPC version was specified. This meant that if the version was unset but the genesis commitment was set, that no header was written and the genesis commitment was ignored.
…ethods (#1298) Write RPC requests are now required to contain the network's genesis commitment as part of their ACCEPT header.
* chore: unify and revisit query limits * review: remove TooMany* error variants * review: update limiter doc & rename MAX_RESPONSE_PAYLOAD_BYTES * review: fix changelog entry * review: create GENERAL_REQUEST_LIMIT const
* feat: track ntx latency * review: fix changelog entries * review: reduce lock risk & improve docs * review: remove pending_latency field
* feat: add explorer to network monitor * review: add warning for tips mismatch * review: make graphql variable a constant * review: move env example to devnet * review: explicit frontend check in frontend * review: abstract copy button & improve tip diff messagE * review: create explorer.rs, improve code readability * fix: remove duplicated changelog entry
* fix: reduce notes limits to 100 * review: fix comment padding Co-authored-by: igamigo <ignacio.amigo@lambdaclass.com> * review: move size comment to struct doc * review: add size related comment to struct docs --------- Co-authored-by: igamigo <ignacio.amigo@lambdaclass.com>
Its because this PR is a merge from If you're seeing different results locally, I suspect its due to our |
This is a tracking PR for v0.13.0 release.