-
Notifications
You must be signed in to change notification settings - Fork 16
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
Decoded value is not same as encoded one #3
Comments
This is absolutely a bug ! |
Thanks. Please note that I don't have this issue if I use the following implementation: https://github.com/ehn-digital-green-development/base45-js |
@dirkx can you merge from https://github.com/ehn-digital-green-development/base45-js and release a new version? I can confirm the current version has several bugs (it fails to decode to the original payload in about 10% of the DGCs I create) and the version at EHN DGC seems to work flawlessly. |
If you want to add another test case that fails in the production version but passes on the EHN DGC version
|
@raziel057 I happened to experience the same issue, it should be fixed in latest main after 1c53b26. |
I have had new decoding problems with 1c53b26, so I moved out to this library which seems to have everything fixed. https://www.npmjs.com/package/base45. |
@vitorpamplona I have not caught any error yet, do you have a test case? |
Sorry, not really. I was basically doing
and when both of them were crashing I just gave up on the lib. |
Hello,
I notice that your code is not working correctly in some cases. For example here:
Produce the following log:
Is it normal that the decoded Uint8Array is not equals to the one provided for encode ?
Please note that the decoded Uint8Array generates an error when using zlib.inflate() function from https://github.com/nodeca/pako, but not the original one:
The text was updated successfully, but these errors were encountered: