md5_hex is failing when there are un-decoded utf8 characters in the input. This has arisen in the _getTagDataForTracks query because grouping may be part of the query. (Example: grouping="Kanka/Klepác")
I wonder if we should apply this to all md5_hex usages in Queries.pm where $p is part of the input string, just to be safe?
md5_hexis failing when there are un-decoded utf8 characters in the input. This has arisen in the_getTagDataForTracksquery because grouping may be part of the query. (Example: grouping="Kanka/Klepác")I wonder if we should apply this to all
md5_hexusages in Queries.pm where$pis part of the input string, just to be safe?