Handling corrupt unicode on annotation creation #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
This is an odd bug! On specific browser, they have noticed that on Label
Studio this gives the following issues:
Note: we don't care about any unicode in annotation, as we don't use
the text for referencing our annotation. So let's just remove any unicode
for now to avoid issue with potentially corrupted unicode.
Test Plan:
We can reproduce this by forcing the annotation end point to consume unicode.
Use the
copy as CURL
option on your browser to copy the "update annotation" call from Label StudioInject some unicode into the CURL command - e.g.