-
Notifications
You must be signed in to change notification settings - Fork 82
feat(ffi): Validate the type of user-defined metadata when deserializing the new IR format. #695
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
Conversation
WalkthroughThe pull request focuses on enhancing error handling in the Changes
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (11)
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
🧹 Nitpick comments (1)
components/core/src/clp/ffi/ir_stream/Deserializer.hpp (1)
173-178
: Consider improving readability of the validation check.While the implementation correctly validates the user-defined metadata, the condition could be more readable.
Consider this more concise version:
- if (metadata_json.contains(cProtocol::Metadata::UserDefinedMetadataKey) - && false == metadata_json.at(cProtocol::Metadata::UserDefinedMetadataKey).is_object()) - { - return std::errc::protocol_not_supported; - } + if (auto it = metadata_json.find(cProtocol::Metadata::UserDefinedMetadataKey); + it != metadata_json.end() && !it->is_object()) + { + return std::errc::protocol_not_supported; + }This version:
- Uses a single find() instead of contains() + at()
- Maintains the same validation logic
- Improves readability while keeping the same functionality
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
components/core/src/clp/ffi/ir_stream/Deserializer.hpp
(2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
components/core/src/clp/ffi/ir_stream/Deserializer.hpp (1)
Pattern **/*.{cpp,hpp,java,js,jsx,ts,tsx}
: - Prefer false == <expression>
rather than !<expression>
.
📓 Learnings (1)
components/core/src/clp/ffi/ir_stream/Deserializer.hpp (1)
Learnt from: LinZhihao-723
PR: y-scope/clp#549
File: components/core/src/clp/ffi/ir_stream/Deserializer.hpp:209-210
Timestamp: 2024-11-10T16:46:53.300Z
Learning: Until #486 is merged with customized error code support, introducing a layer from `IRErrorCode` to `std::errc` is unnecessary.
⏰ Context from checks skipped due to timeout of 90000ms (11)
- GitHub Check: ubuntu-jammy-static-linked-bins
- GitHub Check: ubuntu-focal-static-linked-bins
- GitHub Check: centos-stream-9-static-linked-bins
- GitHub Check: ubuntu-jammy-dynamic-linked-bins
- GitHub Check: ubuntu-focal-dynamic-linked-bins
- GitHub Check: centos-stream-9-dynamic-linked-bins
- GitHub Check: build-macos (macos-14, false)
- GitHub Check: build-macos (macos-14, true)
- GitHub Check: build-macos (macos-13, false)
- GitHub Check: lint-check (ubuntu-latest)
- GitHub Check: build-macos (macos-13, true)
🔇 Additional comments (1)
components/core/src/clp/ffi/ir_stream/Deserializer.hpp (1)
47-50
: LGTM! Documentation clearly specifies the new error condition.The updated documentation accurately reflects the new validation for user-defined metadata format.
For the PR title, how about:
|
Co-authored-by: kirkrodrigues <2454684+kirkrodrigues@users.noreply.github.com>
Description
We've added type checking in #691 to ensure only JSON objects can be serialized as user-defined metadata.
As discussed in clp-ffi-py implementation here, we realized we should also add type checking in the deserialization end to raise invalid typed user-defined metadata.
This PR adds the check to return an error if the user-defined metadata is not a JSON object.
Validation performed
Summary by CodeRabbit
Bug Fixes
Documentation