I'm wondering what writing the backtrace to a /tmp/file and doing a cat -nA on
it would show.
(to get the traceback bits presented by independent alternate formatting
machinery
from what produced what you've seen so far).
On +2025-02-11 19:06:46 +, Christopher Baines wrote:
> Christopher Ba
Christopher Baines writes:
> Christopher Baines writes:
>
>> I've been seeing some strange occasional errors for a while now.
>
> ...
>
>> I'm not sure what the 84 means? If I'm picking out the characters that
>> have failed to be encoded, I'm not sure why some of these would fail
>> (like space
Christopher Baines writes:
> I've been seeing some strange occasional errors for a while now.
...
> I'm not sure what the 84 means? If I'm picking out the characters that
> have failed to be encoded, I'm not sure why some of these would fail
> (like space or w)?
>
> Unfortunately I'm not sure h
Hi,
> (encoding-error put-char conversion to port encoding failed 84
> # s)
Could the error be due to the 7-bit encoding in HTTP headers? [1] The
"84" is EILSEQ from errno.h. [2] Wingo added the functionality here. [3]
I also submitted a patch to resolve in the errno. [4]
A similar issue appear
Hey,
I've been seeing some strange occasional errors for a while now.
Here are some log messages from the guix-build-coordinator:
worker-thread: exception: (encoding-error put-char conversion to port encoding
failed 84 # s)
encoding-error (put-char conversion to port encoding failed 84 # s)
