-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
recv_packet/write_acknowledgement separation #1038
Merged
Merged
Conversation
This file contains 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
… be in separate blocks with forward middleware
agouin
changed the title
recv_packet write_acknowledgement separation
recv_packet/write_acknowledgement separation
Nov 6, 2022
agouin
requested review from
jackzampolin,
jtieri,
boojamya and
mark-rushakoff
as code owners
November 8, 2022 14:06
jtieri
approved these changes
Nov 8, 2022
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.
More great cleanup here!
Comment on lines
-55
to
-78
switch event.Type { | ||
case chantypes.EventTypeRecvPacket, chantypes.EventTypeWriteAck: | ||
pi := &packetInfo{Height: height} | ||
pi.parseAttrs(log, evt.Attributes) | ||
ck, err := processor.PacketInfoChannelKey(event.Type, provider.PacketInfo(*pi)) | ||
if err == nil { | ||
pk := packetKey{ | ||
sequence: pi.Sequence, | ||
channel: ck, | ||
} | ||
_, ok := recvPacketMsgs[pk] | ||
if !ok { | ||
recvPacketMsgs[pk] = pi | ||
} else { | ||
recvPacketMsgs[pk].parseAttrs(log, evt.Attributes) | ||
} | ||
} | ||
default: | ||
m := parseIBCMessageFromEvent(log, evt, chainID, height) | ||
if m == nil || m.info == nil { | ||
// Not an IBC message, don't need to log here | ||
continue | ||
} | ||
messages = append(messages, *m) |
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.
🔥
agouin
added a commit
that referenced
this pull request
Nov 9, 2022
* Separate recv_packet from write_acknowledgement events since they can be in separate blocks with forward middleware * update recv packet info in map * Correlate for flushes * Remove unnecessary change * Fix acks query
agouin
added a commit
that referenced
this pull request
Nov 15, 2022
* Separate recv_packet from write_acknowledgement events since they can be in separate blocks with forward middleware * update recv packet info in map * Correlate for flushes * Remove unnecessary change * Fix acks query
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Separate
recv_packet
fromwrite_acknowledgement
events since they can be in separate blocks with forward middleware.This moves the duty of combining the data from the
write_acknowledgement
event with therecv_packet
event into the path processor, which simplifies the event parser.