-
Notifications
You must be signed in to change notification settings - Fork 100
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
Wrong data pushed for very long literal ByteString #794
Comments
The workaround is to
|
HashedName.zip
and see that constant.Value is
while
Then at
we pushes UTF-8-encoded string, which is c29e0923c2a3c29f515ec29ac28cc3abc389c3bb694bc29ac2bf7e4bc28c3f7ac2b6c3b81b56c3aac2bdc2ac504b08c39c (49 bytes)
The problem is that all syntaxes of literal strings are simply handled as human-readable strings. Actually there can be bytes in a literal string. |
Yes, it seems that it convert the string to UTF8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Many additional 0xC2 and 0xC3 inside, and
9C
instead ofDC
at the end of pushed data.The text was updated successfully, but these errors were encountered: