Closed jaeseung-bae closed 6 months ago
Attention: Patch coverage is 35.48387%
with 20 lines
in your changes are missing coverage. Please review.
Project coverage is 69.53%. Comparing base (
5e2cd7f
) to head (0b9cc3c
).
We should prohibit denoms longer than 255.
Can i have any reason for 255 limit?
We should prohibit denoms longer than 255.
Can i have any reason for 255 limit?
It's because our newly introduced lengthPrefix() assumes it (converts length to byte).
We should prohibit denoms longer than 255.
Can i have any reason for 255 limit?
It's because our newly introduced lengthPrefix() assumes it (converts int to byte).
Thanks for letting me know.
I found regex for denom validation [a-zA-Z][a-zA-Z0-9/-]{2,127}
.
function to get key will be called after validation logic
, so it's okay without length limit.
We should prohibit denoms longer than 255.
Can i have any reason for 255 limit?
It's because our newly introduced lengthPrefix() assumes it (converts int to byte).
Thanks for letting me know.
I found regex for denom validation
[a-zA-Z][a-zA-Z0-9/-]{2,127}
. function to get key will be called aftervalidation logic
, so it's okay without length limit.
I got another case to call without coin validation logic
.
I've just made commit to fix it.
Description
(hello, world)
!=(hell, oworld)
Motivation and context
How has this been tested?
Screenshots (if appropriate):
Checklist:
CHANGELOG.md
client/docs/swagger-ui/swagger.yaml