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: Handle invalid UTF-8 sequences gracefully when converting structured log events to JSON. #52

Merged
merged 4 commits into from
Jan 20, 2025

Conversation

davemarco
Copy link
Contributor

@davemarco davemarco commented Jan 20, 2025

Description

Fixes issue where some files with invalid UTF-8 could not be opened. Now chars are just replaced.

Validation performed

Tested file could now be opened. Tested older IRV2 test file still worked

Summary by CodeRabbit

  • Bug Fixes
    • Improved JSON serialization error handling by replacing invalid UTF-8 characters.
    • Enhanced output formatting for JSON string conversion.

These changes provide a more flexible approach to converting structured data to JSON, ensuring better compatibility and error management during serialization.

@davemarco davemarco requested a review from junhaoliao January 20, 2025 18:29
Copy link

coderabbitai bot commented Jan 20, 2025

Walkthrough

The pull request introduces a new function, dump_json_with_replace, in the StructuredIrStreamReader class within the C++ source code. This function is designed to serialize a JSON value while handling errors by replacing invalid UTF-8 characters instead of throwing exceptions. Additionally, the decode_range method has been updated to utilize this new function for JSON serialization, modifying how JSON strings are generated in terms of error handling and output formatting.

Changes

File Change Summary
src/clp_ffi_js/ir/StructuredIrStreamReader.cpp Added dump_json_with_replace function for JSON serialization; updated decode_range method to use this function instead of direct dump() call

Sequence Diagram

sequenceDiagram
    participant Reader as StructuredIrStreamReader
    participant JSON as JSON Serializer
    
    Reader->>JSON: Prepare JSON serialization
    JSON-->>Reader: Generate JSON string with updated parameters
    Note over JSON: Parameters: 
    Note over JSON: - No specific indentation (-1)
    Note over JSON: - Space as indentation
    Note over JSON: - Error replacement mode
Loading

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9bd54f7 and 2a8e0a6.

📒 Files selected for processing (1)
  • src/clp_ffi_js/ir/StructuredIrStreamReader.cpp (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/clp_ffi_js/ir/StructuredIrStreamReader.cpp
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: lint (ubuntu-latest)
  • GitHub Check: lint (macos-latest)

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>, 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.

CodeRabbit Configuration 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.

@@ -132,7 +133,8 @@ auto StructuredIrStreamReader::decode_range(size_t begin_idx, size_t end_idx, bo
);
json_str = std::string(cEmptyJsonStr);
} else {
json_str = json_result.value().dump();
json_str = json_result.value()
.dump(-1, ' ', false, nlohmann::detail::error_handler_t::replace);
Copy link
Member

@junhaoliao junhaoliao Jan 20, 2025

Choose a reason for hiding this comment

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

Since this is in their example: https://json.nlohmann.me/api/basic_json/error_handler_t/

shall we use the nlohmann::json::error_handler_t::replace alias instead of the one from the detail namespace?

@@ -132,7 +133,8 @@ auto StructuredIrStreamReader::decode_range(size_t begin_idx, size_t end_idx, bo
);
json_str = std::string(cEmptyJsonStr);
} else {
json_str = json_result.value().dump();
json_str = json_result.value()
Copy link
Member

Choose a reason for hiding this comment

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

The magic values seem a bit odd. Shall we consider creating a helper for this? e.g.,

Add this to the anonymous namespace:

constexpr auto cDumpWithReplace = [](auto const& json_obj) {
    return json_obj.dump(-1, ' ', false, nlohmann::json::error_handler_t::replace);
};

Copy link
Member

Choose a reason for hiding this comment

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

As discussed offline, the code should clear enough and there's no need to make a helper. Please ignore this comment.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

See helper I added. I can remove if you'd like. lmk

junhaoliao
junhaoliao previously approved these changes Jan 20, 2025
*/
auto json_dump_with_replace(nlohmann::json const& json) -> std::string;

auto json_dump_with_replace(nlohmann::json const& json) -> std::string {
Copy link
Member

Choose a reason for hiding this comment

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

I'll probably call this dump_json_with_replace but feel free to object


/**
* @see nlohmann::basic_json::dump
* Dumps a JSON value with error handling set to replace invalid UTF-8 characters rather than
Copy link
Member

Choose a reason for hiding this comment

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

Would it be more clear if we say
"Serializes a JSON value into a string with invalid UTF-8 sequences replaced rather than ..."

@davemarco
Copy link
Contributor Author

Okay I tested still works with newer changes. @junhaoliao please approve again and i will merge

Copy link
Member

@junhaoliao junhaoliao left a comment

Choose a reason for hiding this comment

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

for the PR title, how about:

fix: Handle invalid UTF-8 sequences gracefully when converting structured log events to JSON.

since replacement is just an implementation choice.

@davemarco davemarco changed the title fix: Replace invalid UTF-8 bytes instead of throwing exception while converting structured log events to json. fix: Handle invalid UTF-8 sequences gracefully when converting structured log events to JSON. Jan 20, 2025
@davemarco davemarco merged commit 4fc9565 into y-scope:main Jan 20, 2025
4 checks passed
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