Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (409 - 411 of 1030)

Ticket Resolution Summary Owner Reporter
#1320 fixed I/O timeout arguments for TCP sockets are interpreted as milliseconds Max Rottenkolber
Description

(copied from openmcl-devel, see also #1247 as it seems to be related)

Hi folks,

(in Clozure CL 1.10)

could there be a bug in `l1-sockets.lisp:859-860', where timeout values (supposedly in seconds) are not converted to the proper millisecond values used by PROCESS-INPUT-WAIT (`l1-streams.lisp:5449')? The documentation says (emphasis added):

input-timeout---The number of seconds before an input operation times out. Must be a real number between zero and one million. If an input operation takes longer than the specified number of seconds, an input-timeout error is signalled. (see Section 10.1.4, “Stream Timeouts and Deadlines”)

output-timeout---The number of seconds before an output operation times out. Must be a real number between zero and one million. If an output operation takes longer than the specified number of seconds, an output-timeout error is signalled. (see Section 10.1.4, “Stream Timeouts and Deadlines”)

I have not followed the rabbit hole to full length, but I am getting I/O timeout conditions on streams with i/o-timeout == 10 way before 10 seconds. It being actually interpreted as 10 milliseconds would make sense.

Try this to verify (this blocks for 10 seconds when I run it):

(with-open-socket (s :remote-host "mr.gy"

:remote-port 80 :input-timeout (* 10 1000))

(read-line s))

Regards, max

#1407 duplicate (defun nil ...) crashes CCL Max Rottenkolber
Description

Trying to use nil as a function-name in defun crashes CCL 1.11. I think it should signal an error instead. I propose to change ccl::validate-function-name like so:

*** /usr/lib/ccl/level-0/l0-def.lisp
--- #<buffer l0-def.lisp>
***************
*** 118,124 ****
    name))
  
  (defun validate-function-name (name)
!   (if (symbolp name)
      name
      (if (setf-function-name-p name)
        (setf-function-name (cadr name))
--- 118,124 ----
    name))
  
  (defun validate-function-name (name)
!   (if (and (symbolp name) (not (null name)))
      name
      (if (setf-function-name-p name)
        (setf-function-name (cadr name))

I haven’t actually tested this (redefining validate-function-name on a running CCL leads to bootstrapping issues, don’t know how to avoid that).

#915 fixed bad printing of dotted pairs with *print-circle* = t Gary Byers Matt Kaufmann
Description

An extra "." can be printed when *print-circle* is t. A log is below. The version (15230) is the trunk as of two days ago. Not sure how to specify the "component" -- I'd guess it's a source code bug, but I don't know.

Welcome to Clozure Common Lisp Version 1.8-dev-r15230M-trunk  (LinuxX8664)!
? (let* ((*print-circle* t)
	 (atm "hi")
	 (alist `((3 . ,atm) (2 . ,atm))))
    (print alist))

((3 . #1= . "hi") (2 . #1#)) 
((3 . "hi") (2 . "hi"))
? '((3 . #1= . "hi") (2 . #1#))  ; the extra dot ruins readability, of course:

> Error: Reader error on #<CCL::RECORDING-CHARACTER-INPUT-STREAM #x3020006EDE3D>, near position 13:
>        Dot context error in ".".
> While executing: CCL::SIGNAL-READER-ERROR, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options.
1 > :q
? '((3 . #1="hi") (2 . #1#)) ; manual correction
((3 . "hi") (2 . "hi"))
?

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.