-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
ascii85 can't decode what it encodes when the result is large #14
Comments
Can confirm for z85, seem that encoding something along 100K is a browser yields an "undefined" as a encode result. 40K works fine. |
Is this still an issue? I just tested with an 8MB string. In any case this seems like a JS runtime problem, not one of base85. |
Thanks for reporting! Can you please provide a dataset to use which exhibits the issue. |
Ooops, wrong button |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've got a somewhat large binary input (3238814 bytes) that I tried to encode. It encodes fine, but when I try to decode it fails. I tried smaller inputs (<100k) and they all worked. The larger input encodes and decodes fine in the default encoding, but it's a bit of a pain to have to pad out to a multiple of four.
The text was updated successfully, but these errors were encountered: