New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

use byte length, not character length to determine if maxBuffer is exceeded #124

Closed

jedwards1211 opened this issue May 5, 2020 · 1 comment

Assignees

Labels

Member

jedwards1211 commented May 5, 2020

depending on the encoding and output characters, the output buffer could significantly exceed maxBuffer right now.

jedwards1211 added the bug label

jedwards1211 self-assigned this

jedwards1211 closed this as completed in

Member Author

jedwards1211 commented May 8, 2020

🎉 This issue has been resolved in version 4.0.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

jedwards1211 added the released label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment