Conversation
Signed-off-by: Eduardo Silva <eduardo@chronosphere.io>
Signed-off-by: Eduardo Silva <eduardo@chronosphere.io>
Signed-off-by: Eduardo Silva <eduardo@chronosphere.io>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 8 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe YYJSON-to-MessagePack path now limits nesting, propagates packing failures, prevents allocation-size overflow, and cleans up errors. Unit and integration tests cover depth limits and recovery across network ingestion protocols. ChangesYYJSON nesting and recovery
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~30 minutes Change: Bug fix Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 2📝 Generate docstrings 💡
🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2c8bf0a15d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| memory = os.environ.get("VALGRIND") == "1" | ||
| if memory: |
There was a problem hiding this comment.
Honor macOS Leaks mode in the new daemon
When this scenario runs on macOS via run_tests.py --leaks-strict, the runner sets LEAKS and LEAKS_STRICT, but this condition remains false and launches Fluent Bit directly. Consequently, the required memory-safety pass can report success without running Leaks or checking its result; handle LEAKS here or use the suite's existing memory-check wrapper.
AGENTS.md reference: AGENTS.md:L101-L105
Useful? React with 👍 / 👎.
|
High likely a duplicate of #12313 |
Bound shared JSON conversion before recursive descent and propagate MessagePack packing failures. This protects MQTT and inputs using a configured JSON parser, and cleans up partial output when a record cannot be converted.
Validation: Pack and JSON-parser CTest targets passed. The nesting regression fails against the original converter and passes with this change. Defensive network cases for MQTT, TCP/UDP parser and streaming modes, HTTP, Splunk and Forward passed normally and under strict Valgrind; the focused pack boundary test is Valgrind-clean.
Focused integration commands (run against the combined validation build containing these fixes):
Relevant internal CTest targets and focused Valgrind checks also passed. Full PR-range commit-prefix lint, DCO and whitespace checks passed against fetched master. Code and regression tests are separate commits.
Compatibility: JSON containers beyond the configured MessagePack nesting budget (64 in this build) are rejected. Configured parser inputs retain their existing fallback behavior. Public interfaces are unchanged.
Summary by CodeRabbit