grantbuster
commented
2 years ago Note that U32 is a 32char unicode string. Maybe we should check the char length of the original strings before converting. Would all source string formats be the "S30" format? trying to figure out how to parse the int. maybe regex.
This implements a fix for json responses with non-ascii chars, specifically for lambda hsds responses.
For some reason, when there is a json response the S30 dtype breaks on accents and other special characters. I found that you can use a <U32 dtype that works just fine. Pretty sure this doesnt break anything but you can remove the function call if it does end up being bad.