Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Security Level: Public
-
CBG Sprint 84
-
2
Description
The norev message expects sequence to be included as a "sequence", but we're actually writing it with the "seq" property name.
This has implications for ISGR checkpointing that use this field, so the following changes will have to be made:
- If protocol version 2 and client type ISGR - read and write value as "seq"
- Otherwise use "sequence"
If this is being backported to 2.x, we can't do the protocol version check, and should just do a client type check.
Attachments
Issue Links
- Clones
-
CBG-1716 norev message sequence has wrong property name
- Closed