Closed Pitasi closed 4 days ago
[!WARNING]
Rate limit exceeded
@Pitasi has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 33 minutes and 9 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between 20068f8bb9f0beba9cf7670969192cf7b7c30894 and 7aeb887e92176655fb7edeae21a3fdbb6f25f417.
The recent changes primarily involve renaming various entities, functions, and variables to enhance consistency and clarity within the codebase. This includes updating terms related to signature requests and fulfillment, specifically changing Signature
to Sign
across numerous files. Additionally, the updates introduce some new features such as events related to keys, keychains, and sign requests, as well as fixing and improving existing functionalities, including handling sign requests and integrating new technologies.
Files/Paths | Change Summaries |
---|---|
CHANGELOG.md |
Updated terminology for various request-related fields and documented overall changes. |
docs/.spelling , docs/docs/developers/... |
Renamed terminology related to sign requests and fulfillment across documentations. |
docs/docs/learn/keychains/... , docs/static/openapi.yml |
Updated terminologies for keychain operations and API endpoints in the OpenAPI spec. |
go-client/query_client_warden.go , go-client/tx_warden.go |
Renamed request methods and associated message types/functions in the Go client. |
keychain-sdk/sign_requests.go |
Updated function names and references related to pending sign requests. |
proto/warden/warden/v1beta2/... |
Renamed various message types and fields related to sign requests in multiple protobuf files. |
spaceward/src/components/... , spaceward/src/features/... , spaceward/src/hooks/... |
Renamed components and states related to signature requests in the spaceward application. |
tests/cases/keychain_writers.go |
Updated test cases related to sign requests and their identifiers. |
warden/x/warden/keeper/keeper.go , warden/x/warden/keeper/msg_server_fulfil_sign_request.go |
Renamed collections and methods associated with sign requests in the Warden keeper logic. |
sequenceDiagram
participant Client
participant Node
participant Keychain
Client->>+Node: MsgNewSignRequest
Node-->>Client: Acknowledge SignRequest
Node->>Keychain: Broadcast SignRequest
Keychain-->>Node: Awaiting Approval
Node->>Client: Status: Awaiting Approval
Client->>+Node: QuerySignRequests
Node-->>Client: Send List of SignRequests
Client->>+Node: MsgFulfilSignRequest
Node-->>Client: Acknowledge FulfilRequest
Note over Node, Keychain: Processing Signature Fulfillment
Keychain-->>Node: Signature Fulfilled
Node->>Client: Status: Signature Fulfilled
This diagram highlights the interaction flow between the Client, Node, and Keychain for handling new sign requests and fulfilling them, showcasing the updated terminology in the process.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Some renames to make everything more consistent.
They might be breaking changes but if we don't do these now we'll never do :)
Summary by CodeRabbit
New Features
Changes
SignatureRequest
toSignRequest
andUpdateKeyRequest
toFulfilKeyRequest
.Keychain.Fees
type toCoins
.Keychain.IsActive
field.Improvements
Documentation