Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (364 - 366 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

#1330 fixed ~~ does not work properly in FORMAT kylebp
Description

(format nil "~:(a ~~) b~)") should evaluate to "A ~) B", but instead raises an error for premature end of control string.

#1333 fixed stack overflow when inspecting circular data with Mac IDE Martin Brooks
Description

Hello CCL

First I want to thank you for your excellent Lisp. This ticket applies to the Mac IDE for 1.11-r16651 (DarwinX8664).

Having looked at the code for printing, I realize that there are some structural issues that make it more difficult to detect circularity when inspecting. However:

Inspecting a circular list works fine, but if the circles are within structs, CLOS objects, etc., then the inspector generates a stack overflow, and no recovery is possible.

I know you are busy, and perhaps the Mac IDE is not a priority. I have seen that there are efforts underway to build an IDE from Atom. I understand this.

So, if you plan to fix this inspection crash problem for the Mac IDE, I will be glad to wait. But if you are not planning to fix it, then please let me know {brooks.martin@ sympatico.ca} and I will become very motivated to find another way to work with CCL.

thanks, Martin

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