We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
writeBlocksRaw uses the same bounds check as writeBlocksCRLF. writeBlocksRaw will always only write one character while writeBlocksCRLF can write two.
writeBlocksRaw
writeBlocksCRLF
Seems like it should actually be
| n >= len -> commit n True{-needs flush-} False >>= outer s
The text was updated successfully, but these errors were encountered:
Can someone comment on the user-facing impact of this bug?
Sorry, something went wrong.
Under utilization of the char buffer by one byte.
The only time this would cause a problem is if the char buffer had a size of 1 which is never the case.
@mitchellwrosen this is not a vulnerability, just an opportunity to polish.
Successfully merging a pull request may close this issue.
writeBlocksRaw
uses the same bounds check aswriteBlocksCRLF
.writeBlocksRaw
will always only write one character whilewriteBlocksCRLF
can write two.Seems like it should actually be
The text was updated successfully, but these errors were encountered: