-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fixer mixer #122
base: main
Are you sure you want to change the base?
Fixer mixer #122
Conversation
fixed "ADM642" to "AMD64"
fixed "wtether" to "whether"
useless space gap
WalkthroughThe changes in this pull request involve updates to two main files: a GitHub Actions workflow for building Darwin AMD64 and a Go file handling EVM queries. The workflow file corrects a typographical error in the job name and introduces a new environment variable, Changes
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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
🧹 Outside diff range and nitpick comments (2)
.github/workflows/build-darwin-amd64.yml (2)
Line range hint
47-53
: Consider using multi-line command syntaxInstead of using backslashes for line continuation, consider using the more readable multi-line command syntax in GitHub Actions:
- - name: Build and Package for Darwin AMD64 - run: | - cd ../minievm \ - && make build \ - && cd ./build \ - && tar -czvf minievm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz ./minitiad \ - && mv ./minievm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz $GITHUB_WORKSPACE/ \ - && rm -rf ./minitiad + - name: Build and Package for Darwin AMD64 + run: | + cd ../minievm + make build + cd ./build + tar -czvf minievm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz ./minitiad + mv ./minievm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz $GITHUB_WORKSPACE/ + rm -rf ./minitiad🧰 Tools
🪛 actionlint (1.7.3)
48-48: shellcheck reported issue in this script: SC2086:info:5:55: Double quote to prevent globbing and word splitting
(shellcheck)
The
cd ../minievm
navigation is incorrect and needs to be removedThe repository structure shows that we're already in the correct directory with the Makefile present at the root. The
cd ../minievm
command is incorrect as:
- The Makefile exists in the current directory
- There's no
minievm
directory in the parent path- All other build workflow files also incorrectly use this same pattern
The build step should be simplified to:
- name: Build and Package for Darwin AMD64 run: | make build \ && cd ./build \ && tar -czvf minievm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz ./minitiad \ && mv ./minievm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz $GITHUB_WORKSPACE/🔗 Analysis chain
Line range hint
47-53
: Verify the directory navigation logicThe build step contains some concerning directory navigation:
cd ../minievm
moves to the parent directory and then intominievm
. This seems unusual as the repository should already be in the correct directory after checkout.- The artifacts are later moved back to
$GITHUB_WORKSPACE
.Let's verify the repository structure:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check the repository structure to understand the directory navigation # Check if we're already in a minievm directory pwd # List contents of parent directory to see if there's another minievm directory ls -la ../ # Check if Makefile exists in current directory ls -la MakefileLength of output: 644
Script:
#!/bin/bash # Let's check the repository structure and Makefile location more thoroughly # Check the repository root structure ls -la # Check if there's any reference to ../minievm in workflow files rg -l "../minievm" .github/workflows/ # Look for Makefile targets to understand build process grep "^[a-zA-Z].*:" Makefile # Check other workflow files for comparison fd -e yml -e yaml . .github/workflows/ --exec head -n 1 {}Length of output: 3513
🧰 Tools
🪛 actionlint (1.7.3)
48-48: shellcheck reported issue in this script: SC2086:info:5:55: Double quote to prevent globbing and word splitting
(shellcheck)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
api/minievm/evm/v1/query_grpc.pb.go
is excluded by!**/*.pb.go
📒 Files selected for processing (2)
.github/workflows/build-darwin-amd64.yml
(1 hunks)api/minievm/evm/v1/query.pulsar.go
(1 hunks)
🔇 Additional comments (19)
api/minievm/evm/v1/query.pulsar.go (19)
Line range hint 1-1
: LGTM!
The file header comment is correct and appropriate.
Line range hint 2-11
: LGTM!
The import statements are correct and necessary for this generated code file.
Line range hint 13-1322
: LGTM!
The generated code for the QueryCodeRequest
message type looks correct, including:
- Struct definition
- ProtoReflect and slowProtoReflect methods
- Descriptor, Type, Interface, New methods
- Range, Has, Clear, Get, Set, Mutable, NewField methods
- WhichOneof method (though not applicable here)
- GetUnknown, SetUnknown methods
- IsValid method
- ProtoMethods method
No issues found. The code generation appears comprehensive and follows protobuf best practices.
Line range hint 1324-2645
: LGTM!
The generated code for the QueryCodeResponse
message type looks correct, similar to QueryCodeRequest
. No issues found.
Line range hint 2647-4289
: LGTM!
The generated code for the QueryStateRequest
message type looks correct, similar to previous message types. No issues found.
Line range hint 4291-5612
: LGTM!
The generated code for the QueryStateResponse
message type looks correct, similar to previous message types. No issues found.
Line range hint 5614-6614
: LGTM!
The generated code for the QueryERC20FactoryRequest
message type looks correct, similar to previous message types. No issues found.
Line range hint 6616-7937
: LGTM!
The generated code for the QueryERC20FactoryResponse
message type looks correct, similar to previous message types. No issues found.
Line range hint 7939-8939
: LGTM!
The generated code for the QueryERC20WrapperRequest
message type looks correct, similar to previous message types. No issues found.
Line range hint 8941-10262
: LGTM!
The generated code for the QueryERC20WrapperResponse
message type looks correct, similar to previous message types. No issues found.
Line range hint 10264-11585
: LGTM!
The generated code for the QueryContractAddrByDenomRequest
message type looks correct, similar to previous message types. No issues found.
Line range hint 11587-12908
: LGTM!
The generated code for the QueryContractAddrByDenomResponse
message type looks correct, similar to previous message types. No issues found.
Line range hint 12910-14231
: LGTM!
The generated code for the QueryDenomRequest
message type looks correct, similar to previous message types. No issues found.
Line range hint 14233-15554
: LGTM!
The generated code for the QueryDenomResponse
message type looks correct, similar to previous message types. No issues found.
Line range hint 15556-17518
: LGTM!
The generated code for the QueryCallRequest
message type looks correct, including the TraceOptions
field. No issues found.
Line range hint 17520-18840
: LGTM!
The generated code for the TraceOptions
message type looks correct. No issues found.
Line range hint 18842-20805
: LGTM!
The generated code for the QueryCallResponse
message type looks correct, including the repeated Log
field. No issues found.
Line range hint 20807-21807
: LGTM!
The generated code for the QueryParamsRequest
message type looks correct. No issues found.
Line range hint 21809-23130
: LGTM!
The generated code for the QueryParamsResponse
message type looks correct, including the Params
field. No issues found.
Minor Mistakes Fix
This pull request fixes minor typos in three files within the project to improve clarity and professionalism:
.github/workflows/build-darwin-amd64.yml
:Build and Package for Darwin ADM642
toBuild and Package for Darwin AMD64
.api/minievm/evm/v1/query.pulsar.go
:wtether
towhether
.api/minievm/evm/v1/query_grpc.pb.go
:return the function result
toreturn the function result
.These minor adjustments enhance the quality of the project's documentation and workflows.
Author Checklist
I have...
!
in the type prefix if API or client breaking change.Reviewers Checklist
I have...
Allow edits by maintainers.
Summary by CodeRabbit
New Features
Sender
,ContractAddr
,Input
,Value
, andTraceOptions
in request structures.Bug Fixes
WithStorage
field in theTraceOptions
structure.Improvements