decode-timeout wants a REAL, but explodes if given more than '(unsigned-byte 62)

Bug #1727789 reported by Ethan H. Schwartz on 2017-10-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Low
Unassigned

Bug Description

Trivial to reproduce:

(sb-sys:decode-timeout 9223372036854774807) =>
#<TYPE-ERROR expected-type: (UNSIGNED-BYTE 62) datum: 9223372036854774807000>

This is especially annoying if you accidentally give a huge value to the various sb-thread primitives' timeout argument.

This is from SBCL 1.4.0.220.

Jan Moringen (scymtym) on 2017-12-02
Changed in sbcl:
assignee: nobody → Jan Moringen (scymtym)
importance: Undecided → Low
status: New → Triaged
Jan Moringen (scymtym) on 2017-12-02
Changed in sbcl:
status: Triaged → Fix Committed
Jan Moringen (scymtym) on 2017-12-15
Changed in sbcl:
assignee: Jan Moringen (scymtym) → nobody
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers