Fix the int conversion warning in linter

[KyleJu]

Fix the int conversion warning in Linter, suggested in securego/gosec#1185 (comment). Nolint the intended use of int64 to int conversion

[past]

According to this comment the latest version of golangci-lint should not have many false positives. Can you try first to update ours and see if the errors are gone?

[KyleJu]

According to this comment the latest version of golangci-lint should not have many false positives. Can you try first to update ours and see if the errors are gone?

The false positive case mentioned is an "uint8 -> int" overflow false positive, or "byte to int". In our cases, we are casting int 64 to int 32 intentionally, which doesn't fall into the false positive.

After the upgrade, the linter failed again. Regardless I will update the latest golangci-lint version. Thanks for the comment!

[past]

Ideally we would stop doing the error-prone type casting and use int (or uint64) consistently, but we don't need to block the linter fix on this change.