You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried looking at the code but I haven't quite understood it yet; and, yes it is easy to introduce strictness by mistake.
I switching my code to reading lazy byteStrings and handling the encoding afterward - this avoids exception the issue.
Reading a strict text from a process that produces raw bytes fails due to an encoding error and we get a reasonable exception:
However, if we do the same thing with a lazy text, we get an exception relating to hClose rather than the encoding:
In any case the reading succeeds with either strict or lazy bytestrings (because no text encoding is required):
The text was updated successfully, but these errors were encountered: