search

fukamachi / woo

A fast non-blocking HTTP server on top of libev
http://ultra.wikia.com/wiki/Woo_(kaiju)
MIT License
1.27k stars 96 forks source link

woo.response::current-rfc-1123-timestamp triggers error with SBCL 2.4.6 #113

Closed gibsonf1 closed 2 weeks ago

gibsonf1 commented 2 weeks ago

I've just updated to SBCL 2.4.6, and now the woo.response::current-rfc-1123-timestamp function triggers the following error:

Attempt to modify a read-only object at #xFFF7B8B98.
   [Condition of type SB-SYS:MEMORY-FAULT-ERROR]

The quick workaround for now with local-time library:

(defun woo.response::current-rfc-1123-timestamp ()
    (local-time:format-timestring nil (local-time:now) :format +rfc-1123-format+ :timezone local-time:+gmt-zone+)
    )
fukamachi commented 2 weeks ago

What the commit SHA1 of Woo are you using? It should have been fixed by #106.

gibsonf1 commented 2 weeks ago

It looks we had issues getting that update and we're running old code, thanks!

gibsonf1 commented 2 weeks ago

Eitaro,

Thanks for responding on this (and the great libraries!).  We just updated all libraries to latest with quicklisp but had an issue with the woo update.  Thanks!

My best,

Fred

Fred Gibson

Founder & CEO

mobile: 415.335.8232

1255 Treat Blvd, Suite 300 PMB#4611 Walnut Creek, CA  94597

---- On Sat, 06 Jul 2024 06:13:39 -0700 Eitaro Fukamachi @.***> wrote ---

What the commit SHA1 of Woo are you using? It should have been fixed by https://github.com/fukamachi/woo/pull/106. — Reply to this email directly, https://github.com/fukamachi/woo/issues/113#issuecomment-2211766140, or https://github.com/notifications/unsubscribe-auth/AABQBF3TNUVDDEG4KEAZYITZK7UQHAVCNFSM6AAAAABKLWEEZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRG43DMMJUGA. You are receiving this because you authored the thread.