fix: tx compat #23850
fix: tx compat #23850
Conversation
…-unorderedtx-part-1
…-unorderedtx-part-1
Co-authored-by: yihuang <[email protected]> Co-authored-by: Facundo <[email protected]>
…-unorderedtx-part-1
…-unorderedtx-part-1
…-unorderedtx-part-1
…-unorderedtx-part-1
Co-authored-by: Facundo Medica <[email protected]> Co-authored-by: Alex | Interchain Labs <[email protected]>
…-unorderedtx-part-1
…-unorderedtx-part-1
…-unorderedtx-part-1
…f ssh://github.com/cosmos/cosmos-sdk into technicallyty/backport-6ec53aaf54-unorderedtx-part-1
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| break | ||
| } | ||
| } | ||
| fieldNum := int32(wire >> 3) |
Check failure
Code scanning / gosec
integer overflow conversion uint64 -> uint8 Error
| } | ||
| } | ||
| fieldNum := int32(wire >> 3) | ||
| wireType := int(wire & 0x7) |
Check failure
Code scanning / gosec
integer overflow conversion uint64 -> uint8 Error
| break | ||
| } | ||
| } | ||
| intStringLen := int(stringLen) |
Check failure
Code scanning / gosec
integer overflow conversion uint64 -> uint8 Error
| break | ||
| } | ||
| } | ||
| fieldNum := int32(wire >> 3) |
Check failure
Code scanning / gosec
integer overflow conversion uint64 -> uint8 Error
| } | ||
| } | ||
| fieldNum := int32(wire >> 3) | ||
| wireType := int(wire & 0x7) |
Check failure
Code scanning / gosec
integer overflow conversion uint64 -> uint8 Error
| break | ||
| } | ||
| } | ||
| intStringLen := int(stringLen) |
Check failure
Code scanning / gosec
integer overflow conversion uint64 -> uint8 Error
Description
Closes: #23846
fix from #22723
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!in the type prefix if API or client breaking changeCHANGELOG.mdReviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.
I have...