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

Update indexer README #1482

Merged
merged 3 commits into from
May 10, 2024
Merged

Update indexer README #1482

merged 3 commits into from
May 10, 2024

Conversation

chenyaoy
Copy link
Contributor

@chenyaoy chenyaoy commented May 8, 2024

Changelist

Update indexer README

Test Plan

[Describe how this PR was tested (if applicable)]

Author/Reviewer Checklist

  • If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
  • If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
  • If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
  • If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
  • If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
  • Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

  • Documentation
    • Updated the README with clearer installation instructions.
    • Added new sections on building services and running unit tests.
    • Introduced a build step for services and packages.
    • Refined guidance on running unit tests.

@chenyaoy chenyaoy requested a review from Christopher-Li May 8, 2024 21:06
@chenyaoy chenyaoy force-pushed the chenyao/update-indexer-readme branch from 13f6264 to 6d09d99 Compare May 10, 2024 20:01
Copy link
Contributor

coderabbitai bot commented May 10, 2024

Warning

Rate Limit Exceeded

@chenyaoy has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 10 minutes and 40 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 for further information.

Commits Files that changed from the base of the PR and between 5963e5b and aab8ab6.

Walkthrough

The recent updates primarily focus on enhancing the documentation within the indexer directory. Notable improvements involve providing detailed installation and building instructions, clarifying dependency management steps, introducing a new section for building services and packages, and refining guidance on running unit tests. These changes are designed to streamline the setup process and enhance user understanding.

Changes

File Path Summary of Changes
indexer/README.md Added installation and building sections, clarified dependency installation instructions, introduced build steps, and refined unit testing guidance.

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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

Out of diff range and nitpick comments (17)
indexer/README.md (17)

Line range hint 1-1: Add alt text to the image for accessibility.

- <p align="center"><img src="https://dydx.exchange/icon.svg?" width="256" /></p>
+ <p align="center"><img src="https://dydx.exchange/icon.svg?" alt="dYdX Exchange Icon" width="256" /></p>

Line range hint 16-16: Consider using a more specific term than "ender" to describe the service.


49-49: Consider removing "of" for conciseness: "To build all services and packages, run:"


91-91: Consider removing "of" for conciseness: "First, make sure all services and packages are built with the latest code by running:"


Line range hint 194-194: Correct the verb form for clarity: "comlink will serve API requests from..."

- `comlink` will serving API requests from `http://localhost:3002`.
+ `comlink` will serve API requests from `http://localhost:3002`.

Line range hint 202-202: Correct the verb form for clarity: "socks will accept websocket connections from..."

- `socks` will accepting websocket connections from `http://localhost:3003`.
+ `socks` will accept websocket connections from `http://localhost:3003`.

Line range hint 27-27: Remove trailing spaces.

- 

Line range hint 135-135: Remove trailing spaces.

- 

Line range hint 213-213: Remove trailing spaces.

- 

Line range hint 29-29: Add a blank line above the heading for better readability.

+
### Installation

Line range hint 110-110: Add a blank line below the heading for better readability.

## Adding Packages
+

Line range hint 134-134: Add a blank line below the heading for better readability.

## Adding Services
+

Line range hint 139-139: Add a blank line above and below the heading for better readability.

+
## Running package.json scripts
+

Line range hint 159-159: Add a blank line below the heading for better readability.

## Protos
+

Line range hint 177-177: Add a blank line below the heading for better readability.

# Running Dockerfile locally
+

Line range hint 193-193: Add a blank line below the heading for better readability.

## Deploying
+

Line range hint 201-201: Add a blank line below the heading for better readability.

### Running local V4 node
+
Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 2494557 and 6d09d99.
Files selected for processing (1)
  • indexer/README.md (2 hunks)
Additional Context Used
LanguageTool (6)
indexer/README.md (6)

Near line 16: Try using a synonym here to elevate your writing.
Context: ...dYdX V4 application. The services that make up the V4 Indexer are: - ender: Receives o...


Near line 49: Consider removing “of” to be more concise
Context: ...`` pnpm install ### Build To build all of the services and packages, run: pnpm r...


Near line 54: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...s should be run whenever code is changed and you need to deploy or run the updated c...


Near line 91: Consider removing “of” to be more concise
Context: ...## Running unit tests First, make sure all of the services and packages are built with th...


Near line 194: Modal verbs like ‘can’ or ‘will’ require the following verb to be in its base form.
Context: ...I of locally run Indexer comlink will serving API requests from `http://localhost:300...


Near line 202: Modal verbs like ‘can’ or ‘will’ require the following verb to be in its base form.
Context: ...cket messages from Indexer socks will accepting websocket connections from `http://loca...

Path-based Instructions (1)
indexer/README.md (1)

Pattern **/**: Do not include a walkthrough. For all comments on line changes that are longer than 15 lines, add a prefix to the comment of what lines you are commenting on (for example: "The changes from lines 100 to 200...". Add your comment to be on the last 15 lines of the chunk rather than adding your comment to the entire chunk.

indexer/README.md Outdated Show resolved Hide resolved
indexer/README.md Show resolved Hide resolved
@chenyaoy chenyaoy force-pushed the chenyao/update-indexer-readme branch from 6d09d99 to 31d418f Compare May 10, 2024 20:34
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

Out of diff range and nitpick comments (4)
indexer/README.md (4)

Line range hint 1-1: Add alt text to images for accessibility.

- <p align="center"><img src="https://dydx.exchange/icon.svg?" width="256" /></p>
+ <p align="center"><img src="https://dydx.exchange/icon.svg?" alt="dYdX Exchange Icon" width="256" /></p>

Line range hint 7-7: Add alt text to images for accessibility.

- <img src="https://github.com/dydxprotocol/v4-chain/actions/workflows/indexer-build-test-coverage.yml/badge.svg?branch=main" />
+ <img src="https://github.com/dydxprotocol/v4-chain/actions/workflows/indexer-build-test-coverage.yml/badge.svg?branch=main" alt="Build Test Coverage Status" />

Line range hint 194-194: Correct verb form for modal verb "will".

- `comlink` will serving API requests from `http://localhost:3002`.
+ `comlink` will be serving API requests from `http://localhost:3002`.

Line range hint 202-202: Correct verb form for modal verb "will".

- `socks` will accepting websocket connections from `http://localhost:3003`.
+ `socks` will be accepting websocket connections from `http://localhost:3003`.
Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 6d09d99 and 31d418f.
Files selected for processing (1)
  • indexer/README.md (2 hunks)
Additional Context Used
LanguageTool (6)
indexer/README.md (6)

Near line 16: Try using a synonym here to elevate your writing.
Context: ...dYdX V4 application. The services that make up the V4 Indexer are: - ender: Receives o...


Near line 49: Consider removing “of” to be more concise
Context: ...`` pnpm install ### Build To build all of the services and packages, run: pnpm r...


Near line 54: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...s should be run whenever code is changed and you need to deploy or run the updated c...


Near line 91: Consider removing “of” to be more concise
Context: ...## Running unit tests First, make sure all of the services and packages are built with th...


Near line 194: Modal verbs like ‘can’ or ‘will’ require the following verb to be in its base form.
Context: ...I of locally run Indexer comlink will serving API requests from `http://localhost:300...


Near line 202: Modal verbs like ‘can’ or ‘will’ require the following verb to be in its base form.
Context: ...cket messages from Indexer socks will accepting websocket connections from `http://loca...

Path-based Instructions (1)
indexer/README.md (1)

Pattern **/**: Do not include a walkthrough. For all comments on line changes that are longer than 15 lines, add a prefix to the comment of what lines you are commenting on (for example: "The changes from lines 100 to 200...". Add your comment to be on the last 15 lines of the chunk rather than adding your comment to the entire chunk.

Additional comments not posted (2)
indexer/README.md (2)

48-48: Add a blank line below the heading for better readability.


54-54: Add a comma before "and" to connect two independent clauses.

indexer/README.md Outdated Show resolved Hide resolved
indexer/README.md Outdated Show resolved Hide resolved
@chenyaoy chenyaoy force-pushed the chenyao/update-indexer-readme branch from 31d418f to 5963e5b Compare May 10, 2024 20:40
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 31d418f and 5963e5b.
Files selected for processing (1)
  • indexer/README.md (2 hunks)
Additional Context Used
LanguageTool (6)
indexer/README.md (6)

Near line 16: Try using a synonym here to elevate your writing.
Context: ...dYdX V4 application. The services that make up the V4 Indexer are: - ender: Receives o...


Near line 49: Consider removing “of” to be more concise
Context: ...`` pnpm install ### Build To build all of the services and packages, run: pnpm r...


Near line 54: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...s should be run whenever code is changed and you need to deploy or run the updated c...


Near line 91: Consider removing “of” to be more concise
Context: ...## Running unit tests First, make sure all of the services and packages are built with th...


Near line 194: Modal verbs like ‘can’ or ‘will’ require the following verb to be in its base form.
Context: ...I of locally run Indexer comlink will serving API requests from `http://localhost:300...


Near line 202: Modal verbs like ‘can’ or ‘will’ require the following verb to be in its base form.
Context: ...cket messages from Indexer socks will accepting websocket connections from `http://loca...

Path-based Instructions (1)
indexer/README.md (1)

Pattern **/**: Do not include a walkthrough. For all comments on line changes that are longer than 15 lines, add a prefix to the comment of what lines you are commenting on (for example: "The changes from lines 100 to 200...". Add your comment to be on the last 15 lines of the chunk rather than adding your comment to the entire chunk.

Additional comments not posted (4)
indexer/README.md (4)

48-48: Add a blank line below the "Build" heading for better readability.


49-49: Consider removing "of" to be more concise.


54-54: Add a comma before "and" to connect two independent clauses.


91-91: Consider removing "of" to be more concise.

chenyaoy and others added 2 commits May 10, 2024 16:52
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@chenyaoy chenyaoy merged commit c48f03d into main May 10, 2024
11 checks passed
@chenyaoy chenyaoy deleted the chenyao/update-indexer-readme branch May 10, 2024 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants