INFOPLAT-2875: OtelZap refactor zap->otel conversion#1637
Merged
Conversation
|
👋 kirqz23, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
✅ API Diff Results - No breaking changes |
jmank88
requested changes
Oct 22, 2025
jmank88
reviewed
Oct 22, 2025
jmank88
approved these changes
Oct 22, 2025
kirqz23
changed the title
hendoxc
approved these changes
Oct 22, 2025
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Problem
The
mapZapFieldfunction in the otelzap package can panic when processing certain zap fields, particularly when dealing with nil values that implement interfaces like Stringer or error.Zap's logging framework records type information but may store nil pointers in the Interface field of zapcore. When our code attempts to call methods on these nil pointers String(), it results in a runtime panic that can crash the application.