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

chore: remove repeat word #2538

Closed
wants to merge 1 commit into from
Closed

chore: remove repeat word #2538

wants to merge 1 commit into from

Conversation

costcould
Copy link
Contributor

@costcould costcould commented Jun 5, 2024

Description

remove repeat word


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • added appropriate labels to the PR
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

Summary by CodeRabbit

  • New Features

    • Introduced scripts to check for incorrect usage of "a" or "an," duplicate words, and HTML tags in text files.
    • Added scripts to automate cloning of Ethereum, Go, and Rust-related repositories from GitHub.
  • Bug Fixes

    • Corrected typos in comments and error messages across various scripts and test files to improve clarity and accuracy.

Signed-off-by: costcould <[email protected]>
@costcould costcould requested a review from a team as a code owner June 5, 2024 08:10
Copy link
Contributor

coderabbitai bot commented Jun 5, 2024

Walkthrough

The recent changes primarily involve the enhancement and bug fixes of various Bash scripts and Go files. The updates include typo corrections, comment improvements, and the addition of new functionalities within scripts for checking text patterns and cloning repositories. Overall, the changes aim to improve script accuracy, maintainability, and functionality without altering the core declarations of the exported or public entities.

Changes

File/Directory Change Summary
check_a_or_an.sh Added functionality to check and correct the usage of "a" or "an" before words.
check_dup_word.sh Implemented a script to identify duplicate consecutive words in text files.
check_html_tag.sh Updated to include commands for searching various HTML tags within files.
get_all_eth.sh, get_all_go.sh, get_all_rust.sh Added scripts to clone multiple repositories related to Ethereum, Go, and Rust into new directories.
x/incentive/keeper/scenario_test.go Updated comments related to unbonding supply and reward distribution.
x/leverage/types/keys.go Corrected a typo in the function name related to key generation.
x/leverage/types/token.go Fixed a typo in an error message within the Token validation function.
x/uibc/quota/quota_test.go Corrected a typo in a comment about a transfer operation.

Poem

In scripts and codes, where errors lay,
We've swept the bugs and typos away.
From "a" to "an" and tags to seek,
Our scripts now stand robust and sleek.
With Go and Rust, and Ethereum's might,
We've cloned the worlds, set code alight.
A realm of code, now clean and bright! ✨🐇


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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @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: 10

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 19ce5ee and 88b6ed9.

Files selected for processing (10)
  • check_a_or_an.sh (1 hunks)
  • check_dup_word.sh (1 hunks)
  • check_html_tag.sh (1 hunks)
  • get_all_eth.sh (1 hunks)
  • get_all_go.sh (1 hunks)
  • get_all_rust.sh (1 hunks)
  • x/incentive/keeper/scenario_test.go (1 hunks)
  • x/leverage/types/keys.go (1 hunks)
  • x/leverage/types/token.go (1 hunks)
  • x/uibc/quota/quota_test.go (1 hunks)
Files skipped from review due to trivial changes (6)
  • check_dup_word.sh
  • check_html_tag.sh
  • x/incentive/keeper/scenario_test.go
  • x/leverage/types/keys.go
  • x/leverage/types/token.go
  • x/uibc/quota/quota_test.go
Additional context used
Shellcheck
check_a_or_an.sh

[error] 10-10: Double quote array expansions to avoid re-splitting elements. (SC2068)


[info] 12-12: Double quote to prevent globbing and word splitting. (SC2086)


[error] 28-28: Double quote array expansions to avoid re-splitting elements. (SC2068)


[info] 30-30: Double quote to prevent globbing and word splitting. (SC2086)

get_all_rust.sh

[warning] 5-5: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)


[warning] 8-8: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)

get_all_eth.sh

[warning] 4-4: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)


[warning] 7-7: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)

get_all_go.sh

[warning] 4-4: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)


[warning] 7-7: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)


for item in ${not_a_array[@]}
do
ag "a "$item
Copy link
Contributor

Choose a reason for hiding this comment

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

Double quote the pattern in ag command to prevent globbing and word splitting.

-  ag "a "$item
+  ag "a $item"
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
ag "a "$item
ag "a $item"
Tools
Shellcheck

[info] 30-30: Double quote to prevent globbing and word splitting. (SC2086)


for item in ${not_an_array[@]}
do
ag "an "$item
Copy link
Contributor

Choose a reason for hiding this comment

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

Double quote the pattern in ag command to prevent globbing and word splitting.

-  ag "an "$item
+  ag "an $item"
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
ag "an "$item
ag "an $item"
Tools
Shellcheck

[info] 12-12: Double quote to prevent globbing and word splitting. (SC2086)

not_an_array=(user utility unique useful url union uvarint uniform usage uid unified utilization unit unix utilized usual uintptr uint)


for item in ${not_an_array[@]}
Copy link
Contributor

Choose a reason for hiding this comment

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

Ensure array expansions are double-quoted to prevent word splitting.

- for item in ${not_an_array[@]}
+ for item in "${not_an_array[@]}"
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
for item in ${not_an_array[@]}
for item in "${not_an_array[@]}"
Tools
Shellcheck

[error] 10-10: Double quote array expansions to avoid re-splitting elements. (SC2068)

not_a_array=(http heir herb honest honesty honorable hour honor MBA FBI herb hypothesis historic hourglass xml)


for item in ${not_a_array[@]}
Copy link
Contributor

Choose a reason for hiding this comment

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

Ensure array expansions are double-quoted to prevent word splitting.

- for item in ${not_a_array[@]}
+ for item in "${not_a_array[@]}"
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
for item in ${not_a_array[@]}
for item in "${not_a_array[@]}"
Tools
Shellcheck

[error] 28-28: Double quote array expansions to avoid re-splitting elements. (SC2068)

cd ~
mkdir new-rust

cd new-rust
Copy link
Contributor

Choose a reason for hiding this comment

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

Add error handling for cd command to ensure script exits if directory change fails.

- cd new-rust
+ cd new-rust || exit
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
cd new-rust
cd new-rust || exit
Tools
Shellcheck

[warning] 8-8: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)



#cd /Users/fliter
cd ~
Copy link
Contributor

Choose a reason for hiding this comment

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

Add error handling for cd command to ensure script exits if directory change fails.

- cd ~
+ cd ~ || exit
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
cd ~
cd ~ || exit
Tools
Shellcheck

[warning] 5-5: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)

cd ~
mkdir new-eth

cd new-eth
Copy link
Contributor

Choose a reason for hiding this comment

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

Add error handling for cd command to ensure script exits if directory change fails.

- cd new-eth
+ cd new-eth || exit
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
cd new-eth
cd new-eth || exit
Tools
Shellcheck

[warning] 7-7: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)

#!/bin/bash

#cd /Users/fliter
cd ~
Copy link
Contributor

Choose a reason for hiding this comment

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

Add error handling for cd command to ensure script exits if directory change fails.

- cd ~
+ cd ~ || exit
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
cd ~
cd ~ || exit
Tools
Shellcheck

[warning] 4-4: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)

cd ~
mkdir new-go

cd new-go
Copy link
Contributor

Choose a reason for hiding this comment

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

Add error handling for cd command to ensure script exits if directory change fails.

- cd new-go
+ cd new-go || exit
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
cd new-go
cd new-go || exit
Tools
Shellcheck

[warning] 7-7: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)

#!/bin/bash

#cd /Users/fliter
cd ~
Copy link
Contributor

Choose a reason for hiding this comment

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

Add error handling for cd command to ensure script exits if directory change fails.

- cd ~
+ cd ~ || exit
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
cd ~
cd ~ || exit
Tools
Shellcheck

[warning] 4-4: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. (SC2164)

Copy link
Member

@robert-zaremba robert-zaremba left a comment

Choose a reason for hiding this comment

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

Please remove all the scripts and propose only changes in the *.go files

Copy link

stale bot commented Jul 7, 2024

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the S:Stale label Jul 7, 2024
@stale stale bot closed this Jul 14, 2024
@costcould
Copy link
Contributor Author

Please remove all the scripts and propose only changes in the *.go files

Thanks. The new pr #2579

Please review again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants