Closed jackysp closed 2 years ago
@jackysp I get the same problem in version 1.17, it is normal to use 1.16. I guess it may be related to this change in 1.17:
The Writer.WriteRune method now writes the replacement character U+FFFD for negative rune values, as it does for other invalid runes.
https://github.com/pingcap/tidb/pull/29846 fixed it in TiDB repo. @freeman983
Question
Invalid characters generated by goyacc?
happened in 48d84c1db4287c2649f9a38b3b23a55c4bd528b5