Skip to content
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

Fix character_not_in_repertoire error for tx revert reason #5411

Merged
merged 1 commit into from
Apr 5, 2022

Conversation

nikitosing
Copy link
Member

@nikitosing nikitosing commented Apr 4, 2022

Close #5409

Changelog

Bug Fixes

  • Add check: if revert reason is valid UTF-8 string then leave as UTF-8, otherwise save as raw hex string

Checklist for your Pull Request (PR)

@nikitosing nikitosing force-pushed the np-fix-crash-on-invalid-utf-revert branch from a5458be to 09b323b Compare April 4, 2022 17:00
@nikitosing nikitosing requested a review from vbaranov April 4, 2022 17:21
@vbaranov vbaranov force-pushed the np-fix-crash-on-invalid-utf-revert branch from 09b323b to b82f9bd Compare April 5, 2022 16:13
@vbaranov vbaranov merged commit 253bad8 into master Apr 5, 2022
@vbaranov vbaranov deleted the np-fix-crash-on-invalid-utf-revert branch April 5, 2022 16:33
sidhujag pushed a commit to syscoin/blockscout that referenced this pull request Apr 6, 2022
…valid-utf-revert

Fix character_not_in_repertoire error for tx revert reason
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tx page: ERROR 22021 (character_not_in_repertoire) invalid byte sequence for encoding "UTF8"
2 participants