GNU bug report logs -
#62590
Strange put-char encoding-error "conversion to port encoding failed"
Previous Next
To reply to this bug, email your comments to 62590 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guile <at> gnu.org
:
bug#62590
; Package
guile
.
(Sat, 01 Apr 2023 11:44:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Christopher Baines <mail <at> cbaines.net>
:
New bug report received and forwarded. Copy sent to
bug-guile <at> gnu.org
.
(Sat, 01 Apr 2023 11:44:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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 #<output: file 1> s)
encoding-error (put-char conversion to port encoding failed 84 #<output: file 1> s)
encoding-error (put-char conversion to port encoding failed 84 #<output: file 1> w)
encoding-error (put-char conversion to port encoding failed
84 #<output: file 1> 2
encoding-error (put-char conversion to port encoding fencoding-error (put-char conversion to port encoding failed 84 #<o
utput: file 1> w)
encoding-error (put-char conversion to port encoding failed 84 #<output: file 1> w)
2022-10-02 17:23:38 (ERROR): error running build-success hook: encoding-error (put-char conversion to port encoding failed
84 #<output: file 1> B)
Throw to key `encoding-error' with args `("put-char" "conversion to port encoding failed" 84 #<output: file 1> #\p)'.
2022-10-02 21:21:37 (ERROR): error running build-success hook: misc-error (#f ~A (error: command failed (1): (/gnu/store/6
Throw to key `encoding-error' with args `("put-char" "conversion to port encoding failed" 84 #<output: file 1> #\space)'.
Throw to key `encoding-error' with args `("put-char" "conversion to port encoding failed" 84 #<output:
file 1> #\2)'.
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 how to reproduce this. Suspendable ports
might be a factor here as that is probably in use.
Information forwarded
to
bug-guile <at> gnu.org
:
bug#62590
; Package
guile
.
(Sun, 21 Jan 2024 04:02:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 62590 <at> debbugs.gnu.org (full text, mbox):
Hi,
> (encoding-error put-char conversion to port encoding failed 84
> #<output: file 1> 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 appeared in Guix's Cuirass. [5]
Kind regards
Felix
[1] https://lists.gnu.org/archive/html/guile-user/2020-09/msg00015.html
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/uapi/asm-generic/errno.h#n67
[3] https://git.savannah.gnu.org/cgit/guile.git/commit/?id=43b6feeb1adafe54170304e7cc3c29a15c1d3808
[4] https://debbugs.gnu.org/68624
[5] https://debbugs.gnu.org/59510
This bug report was last modified 344 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.