fix(tllogger): log PutFull data on A channel#149
Merged
Conversation
wakafa1
approved these changes
May 25, 2026
zzQGyy
pushed a commit
that referenced
this pull request
May 30, 2026
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
2 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.
We support Put for XSAI, so log Put data in TLLogger is required for checking data correctness
This pull request introduces a targeted update to the logging functionality in the TileLink utility logger. The main change ensures that data is only logged for specific message types, improving both the accuracy and efficiency of logging.
Logging improvements:
logAmethod inTLLoggerto assigna.datatolog.dataonly when the opcode matchesTLMessages.PutFullData, ensuring that data is logged selectively for relevant message types.