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

fix(torii-grpc): nullable enum array deser #2887

Merged
merged 2 commits into from
Jan 10, 2025

Conversation

Larkooo
Copy link
Collaborator

@Larkooo Larkooo commented Jan 10, 2025

Summary by CodeRabbit

  • Bug Fixes

    • Improved error handling for processing empty serialized arrays
  • Chores

    • Added logging for SQL query execution to assist with debugging

Copy link

coderabbitai bot commented Jan 10, 2025

Pull Request Analysis

Ohayo, sensei! Let's dive into the changes with precision and clarity.

Walkthrough

The pull request introduces modifications to the crates/torii/sqlite/src/model.rs file, focusing on improving error handling for empty serialized arrays. A new conditional check is added in the map_row_to_ty function to set the ty variable to an empty vector and return early if the serialized_array string is empty. This change enhances the control flow by preventing attempts to deserialize an empty string into a JSON value. The fetch_entities function remains unchanged in logic and structure.

Changes

File Change Summary
crates/torii/sqlite/src/model.rs - Added early exit condition for empty serialized_array in map_row_to_ty function
- fetch_entities function remains unchanged

Sequence Diagram

sequenceDiagram
    participant Func as map_row_to_ty
    participant Array as Serialized Array
    
    Func->>Array: Check array content
    alt Empty Array
        Func-->>Func: Early return with empty vector
    else Non-Empty Array
        Func->>Func: Continue normal processing
    end
Loading

The sequence diagram illustrates the new control flow for handling empty serialized arrays, showing the early return mechanism when an empty array is detected.


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 928f90c and 5c74ad2.

📒 Files selected for processing (1)
  • crates/torii/sqlite/src/model.rs (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • crates/torii/sqlite/src/model.rs

🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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

@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: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4371331 and 928f90c.

📒 Files selected for processing (1)
  • crates/torii/sqlite/src/model.rs (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build
  • GitHub Check: docs
  • GitHub Check: clippy
🔇 Additional comments (1)
crates/torii/sqlite/src/model.rs (1)

379-382: Ohayo! Nice defensive programming, sensei!

The early return for empty serialized arrays is a good addition that prevents potential deserialization errors.

@@ -533,6 +537,7 @@ pub async fn fetch_entities(
query += &format!(" OFFSET {}", offset);
}

println!("{}", query);
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider using a proper logging framework instead of println

Ohayo! While logging the SQL query is helpful for debugging, using println! in production code isn't ideal. Consider using the tracing or log crate instead, which provides structured logging with different log levels.

-            println!("{}", query);
+            tracing::debug!(?query, "executing fetch query");
📝 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. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
println!("{}", query);
tracing::debug!(?query, "executing fetch query");

Copy link

codecov bot commented Jan 10, 2025

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 55.81%. Comparing base (4371331) to head (5c74ad2).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
crates/torii/sqlite/src/model.rs 0.00% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2887      +/-   ##
==========================================
- Coverage   55.82%   55.81%   -0.02%     
==========================================
  Files         449      449              
  Lines       57693    57697       +4     
==========================================
- Hits        32206    32201       -5     
- Misses      25487    25496       +9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Larkooo Larkooo enabled auto-merge (squash) January 10, 2025 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants