-
Notifications
You must be signed in to change notification settings - Fork 28
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
fix/update_protobuf_version #324
Conversation
…ges in the latest protobuf library version
WalkthroughThe version 1.5.1 update brings significant changes to the project, focusing on transitioning from Changes
Recent Review DetailsConfiguration used: .coderabbit.yaml Files selected for processing (1)
Files skipped from review due to trivial changes (1)
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: pypi/[email protected] |
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: 2
@@ -2,6 +2,10 @@ | |||
|
|||
All notable changes to this project will be documented in this file. | |||
|
|||
## [1.5.1] - 2024-05-02 | |||
### Changed | |||
- Updated calls to `json_format.MessageToDict` for compliance with the new version of the `protobuf` library |
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.
Add a space after the period in the sentence for better readability.
- - Updated calls to `json_format.MessageToDict` for compliance with the new version of the `protobuf` library
+ - Updated calls to `json_format.MessageToDict` for compliance with the new version of the `protobuf` library.
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.
- Updated calls to `json_format.MessageToDict` for compliance with the new version of the `protobuf` library | |
- Updated calls to `json_format.MessageToDict` for compliance with the new version of the `protobuf` library. |
[0x1af8fa374392dc1bd6331f38f0caa424a39b05dd9dfdc7a2a537f6f62bde50fe] | ||
description = 'Mainnet Spot USDe/USDT' | ||
base = 18 | ||
quote = 6 | ||
min_price_tick_size = 0.0000000000000001 | ||
min_display_price_tick_size = 0.0001 | ||
min_quantity_tick_size = 100000000000000000 | ||
min_display_quantity_tick_size = 0.1 |
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.
Tip
Codebase Verification
The output from the script indicates that the entity ID [0x1af8fa374392dc1bd6331f38f0caa424a39b05dd9dfdc7a2a537f6f62bde50fe]
appears in numerous files across the repository. This suggests that the entity ID is not unique, which contradicts the expectation of uniqueness for such identifiers in the system.
Given this information, it is clear that there are issues with the uniqueness of the entity ID as it is used across multiple files and contexts within the codebase. This could potentially lead to conflicts or errors in the system where this ID is expected to uniquely identify an entity.
Conclusion:
- The entity ID
[0x1af8fa374392dc1bd6331f38f0caa424a39b05dd9dfdc7a2a537f6f62bde50fe]
is not unique within the system as it appears in multiple files. - This could lead to potential conflicts or errors in the system.
Recommendation:
- Review the usage of this entity ID across the system to ensure that it does not lead to unintended behavior or conflicts.
- Consider assigning a unique ID to the new entity to avoid overlap with existing entities.
Analysis chain
New entity [0x1af8fa374392dc1bd6331f38f0caa424a39b05dd9dfdc7a2a537f6f62bde50fe]
(USDe/USDT) added with detailed specifications. Confirm that the new entity's settings are appropriate for its market strategy and that the entity ID is unique within the system.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the uniqueness of the new entity ID and appropriateness of settings.
# Check for duplicate entity IDs.
rg --files-with-matches --type ini $'[0x1af8fa374392dc1bd6331f38f0caa424a39b05dd9dfdc7a2a537f6f62bde50fe]' | while read file; do
# Test: Search for duplicate entity IDs to ensure uniqueness. Expect: No matches except current file.
ast-grep --lang ini --pattern $'[0x1af8fa374392dc1bd6331f38f0caa424a39b05dd9dfdc7a2a537f6f62bde50fe]' "$file"
done
Length of output: 147
Script:
#!/bin/bash
# Description: Re-verify the uniqueness of the new entity ID.
# Corrected command to search for the entity ID across all files, not just .ini since 'ini' is not a recognized type by `rg`.
rg '[0x1af8fa374392dc1bd6331f38f0caa424a39b05dd9dfdc7a2a537f6f62bde50fe]' -l
Length of output: 50954
…xes for macos runners
json_format.MessageToDict
for compliance with the new version of theprotobuf
librarySummary by CodeRabbit
New Features
Bug Fixes
Documentation
Refactor