[pull] master from DataDog:master - #461
Merged
Merged
Conversation
…3130) * fix(ibm_mq): handle non-UTF-8 description fields without crashing IBM MQ queue managers may store channel and queue description fields (MQCACH_DESC, MQCA_Q_DESC) in non-UTF-8 encodings (e.g. Latin-1, Windows code pages) because they are free-form text entered by administrators. The previous code called to_string() which unconditionally decoded bytes as UTF-8, raising UnicodeDecodeError when the data didn't conform. Adds decode_mq_description() in utils.py that tries UTF-8 first and falls back to UTF-8 with errors='replace' on failure, logging a debug message so the issue is visible without crashing the check. Fixes: AGENT-15938 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore(ibm_mq): rename changelog entry to match PR number Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix case * Add changelog
* Add AST-based expression validation for query extras * changelog * lint * improve log messages and tests * update changelog * address agint-review
* [Release] Bumped datadog_checks_base version to 37.34.1 * [Release] Update metadata
we support Postgres 18
* [LOGSC-2385] Add bypass annotations for new linter checks We’re enabling new linter rules and some integrations are expected to remain non‑compliant. Add permanent bypass annotations so CI stays green and not fail for new PRs. * Revert "[LOGSC-2385] Add bypass annotations for new linter checks" This reverts commit a0a65b9. * update
* kafka_actions: Add raw message format with base64 encoding for key and value Support 'raw' as a value_format and key_format for read_messages action. Raw bytes are returned as base64-encoded strings, enabling consumption of binary messages that don't conform to JSON, BSON, string, Avro, or Protobuf formats. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Fix changelog entry PR number Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Fix raw format coercion: wrap base64 in json.dumps to survive _parse_deserialized Certain byte sequences produce base64 strings like "null", "true", or "1234" that json.loads would coerce into None, True, or int. Wrapping in json.dumps ensures _parse_deserialized always returns a string. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ring (#23106) * [kafka_actions] Base64-encode binary headers and support header filtering Binary Kafka headers were displayed as unhelpful `<binary, N bytes>` placeholders. Now they are base64-encoded with a `<base64>` prefix so the actual data is visible. Header filtering is now supported in both filter systems: - jq-style: `.headers.dbmOrgId == "2"` - MessageFilter: `field: "header.dbmOrgId", operator: "eq", value: "2"` Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Remove unnecessary MessageFilter header filtering MessageFilter is not used anywhere in the codebase. Only the jq-style filter in check.py is used, so header filtering only needs to be there. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Use lazy dict for filter context to preserve partial deserialization The filter context was eagerly accessing deserialized_msg.key and deserialized_msg.value, defeating the lazy deserialization. Now uses _LazyMessageDict which only triggers deserialization when the filter actually accesses a field (e.g., filtering on .headers won't deserialize key/value). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Add changelog entry for header improvements Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )