From jingtaozf at gmail.com Fri Sep 24 05:51:41 2010 From: jingtaozf at gmail.com (Xu Jingtao) Date: Fri, 24 Sep 2010 13:51:41 +0800 Subject: [elephant-devel] elephant 1.0 is unstable under Clozure Common Lisp Version 1.5-r13651 (LinuxX8632) Message-ID: <4c9c3d53.013f970a.75cb.5b48@mx.google.com> hi elephant-dev: I use elephant 1.0 under Clozure Common lisp,and exception often occurs like this: =============================================== There is no applicable method for the generic function: # when called with arguments: (NIL) (B2D527D4) : 0 (PRINT-CALL-HISTORY :CONTEXT NIL :PROCESS NIL :ORIGIN NIL :DETAILED-P NIL :COUNT 536870911 :START-FRAME-NUMBER 0 :STREAM # :PRINT-LEVEL 2 :PRINT-LENGTH 5 :SHOW-INTERNAL-FRAMES NIL :FORMAT :TRADITIONAL) 735 (B2D52888) : 1 (PRINT-BACKTRACE-TO-STREAM #) 71 (B2D528A0) : 2 (GET-BACKTRACE) 327 (B2D528D4) : 3 (FUNCALL #'#<(:INTERNAL (HUNCHENTOOT:HANDLE-REQUEST (HUNCHENTOOT:ACCEPTOR HUNCHENTOOT:REQUEST)))> #) 119 (B2D528F0) : 4 (SIGNAL #) 903 (B2D52918) : 5 (SIGNAL #) 903 (B2D52940) : 6 (%ERROR # NIL -323663258) 119 (B2D52954) : 7 (CERROR "Try calling it again" "There is no applicable method for the generic function:~% ~s~%when called with arguments:~% ~s" # (NIL)) 823 (B2D52998) : 8 (FUNCALL #'#<#> # NIL) 103 (B2D529B8) : 9 (FUNCALL #'#<#> # NIL NIL NIL) 199 (B2D529E4) : 10 (%%STANDARD-COMBINED-METHOD-DCODE (# #) -323663226) 679 (B2D52A2C) : 11 (UPDATE-OBSOLETE-INSTANCE #) 2359 (B2D52A44) : 12 (%%NTH-ARG-DCODE #((#<#> #<#> #<#>) NIL NIL 1 # ...) -323663203) 1415 (B2D52A80) : 13 (FUNCALL #'#<#> # 402 NIL) 223 (B2D52A98) : 14 (FUNCALL #'#<#> # 402) 95 (B2D52AAC) : 15 (FUNCALL #'#<#> # 308 NIL) 743 (B2D52AF8) : 16 (FUNCALL #'#<(:INTERNAL ELEPHANT::MAP-OBJ ELEPHANT:MAP-INVERTED-INDEX)> "test at gmail.com" 308) 47 (B2D52B10) : 17 (FUNCALL #'#<(:INTERNAL #:G18136 ELEPHANT::MAP-BTREE-VALUES)> "test at gmail.com" 308) 39 (B2D52B28) : 18 (FUNCALL #'#<(:INTERNAL ELEPHANT::MAP-BTREE-VALUES)>) 519 (B2D52B88) : 19 (FUNCALL #'#<#> # # :TRANSACTION NIL :PARENT NIL :ENVIRONMENT NIL :RETRIES 200 :RETRY-WAIT 0.1 :DEGREE-2 T :READ-UNCOMMITTED NIL :TXN-NOSYNC NIL :TXN-NOWAIT NIL :TXN-SYNC NIL :SNAPSHOT NIL :INHIBIT-ROLLBACK-FN NIL) 1351 (B2D52C5C) : 20 (MAP-BTREE-VALUES # # "test at gmail.com" T) 719 (B2D52C90) : 21 (FUNCALL #'#<#> # # :VALUE "test at gmail.com" :COLLECT T) 183 (B2D52CD0) : 22 (MAP-INVERTED-INDEX # # XJT-SITE::USER-MAIL :VALUE "test at gmail.com" :COLLECT T) 799 (B2D52D2C) : 23 (url=/license/user-center) 119 =============================================== I can retry my operation and the error will not occur the next time. why and how to fix this? best regards. jingtao. From eslick at media.mit.edu Fri Sep 24 06:04:31 2010 From: eslick at media.mit.edu (Ian Eslick) Date: Thu, 23 Sep 2010 23:04:31 -0700 Subject: [elephant-devel] elephant 1.0 is unstable under Clozure Common Lisp Version 1.5-r13651 (LinuxX8632) In-Reply-To: <4c9c3d53.013f970a.75cb.5b48@mx.google.com> References: <4c9c3d53.013f970a.75cb.5b48@mx.google.com> Message-ID: Did you have this problem in 1.4? We use Elephant extensively on Clozure on Mac/Linux under 1.4 but I haven't upgraded to the latest 1.5 on any system that I'm aware of. There are some occasional bugs found in the schema management code too that may be lurking. Ian On Sep 23, 2010, at 10:51 PM, Xu Jingtao wrote: > hi elephant-dev: > I use elephant 1.0 under Clozure Common lisp,and exception often occurs > like this: > =============================================== > There is no applicable method for the generic function: > # > when called with arguments: > (NIL) > (B2D527D4) : 0 (PRINT-CALL-HISTORY :CONTEXT NIL :PROCESS NIL :ORIGIN NIL :DETAILED-P NIL :COUNT 536870911 :START-FRAME-NUMBER 0 :STREAM # :PRINT-LEVEL 2 :PRINT-LENGTH 5 :SHOW-INTERNAL-FRAMES NIL :FORMAT :TRADITIONAL) 735 > (B2D52888) : 1 (PRINT-BACKTRACE-TO-STREAM #) 71 > (B2D528A0) : 2 (GET-BACKTRACE) 327 > (B2D528D4) : 3 (FUNCALL #'#<(:INTERNAL (HUNCHENTOOT:HANDLE-REQUEST (HUNCHENTOOT:ACCEPTOR HUNCHENTOOT:REQUEST)))> #) 119 > (B2D528F0) : 4 (SIGNAL #) 903 > (B2D52918) : 5 (SIGNAL #) 903 > (B2D52940) : 6 (%ERROR # NIL -323663258) 119 > (B2D52954) : 7 (CERROR "Try calling it again" "There is no applicable method for the generic function:~% ~s~%when called with arguments:~% ~s" # (NIL)) 823 > (B2D52998) : 8 (FUNCALL #'#<#> # NIL) 103 > (B2D529B8) : 9 (FUNCALL #'#<#> # NIL NIL NIL) 199 > (B2D529E4) : 10 (%%STANDARD-COMBINED-METHOD-DCODE (# #) -323663226) 679 > (B2D52A2C) : 11 (UPDATE-OBSOLETE-INSTANCE #) 2359 > (B2D52A44) : 12 (%%NTH-ARG-DCODE #((#<#> #<#> #<#>) NIL NIL 1 # ...) -323663203) 1415 > (B2D52A80) : 13 (FUNCALL #'#<#> # 402 NIL) 223 > (B2D52A98) : 14 (FUNCALL #'#<#> # 402) 95 > (B2D52AAC) : 15 (FUNCALL #'#<#> # 308 NIL) 743 > (B2D52AF8) : 16 (FUNCALL #'#<(:INTERNAL ELEPHANT::MAP-OBJ ELEPHANT:MAP-INVERTED-INDEX)> "test at gmail.com" 308) 47 > (B2D52B10) : 17 (FUNCALL #'#<(:INTERNAL #:G18136 ELEPHANT::MAP-BTREE-VALUES)> "test at gmail.com" 308) 39 > (B2D52B28) : 18 (FUNCALL #'#<(:INTERNAL ELEPHANT::MAP-BTREE-VALUES)>) 519 > (B2D52B88) : 19 (FUNCALL #'#<#> # # :TRANSACTION NIL :PARENT NIL :ENVIRONMENT NIL :RETRIES 200 :RETRY-WAIT 0.1 :DEGREE-2 T :READ-UNCOMMITTED NIL :TXN-NOSYNC NIL :TXN-NOWAIT NIL :TXN-SYNC NIL :SNAPSHOT NIL :INHIBIT-ROLLBACK-FN NIL) 1351 > (B2D52C5C) : 20 (MAP-BTREE-VALUES # # "test at gmail.com" T) 719 > (B2D52C90) : 21 (FUNCALL #'#<#> > # # :VALUE "test at gmail.com" :COLLECT T) 183 > (B2D52CD0) : 22 (MAP-INVERTED-INDEX # # XJT-SITE::USER-MAIL :VALUE "test at gmail.com" :COLLECT T) 799 > (B2D52D2C) : 23 (url=/license/user-center) 119 > =============================================== > > I can retry my operation and the error will not occur the next time. > why and how to fix this? > > best regards. > jingtao. > > _______________________________________________ > elephant-devel site list > elephant-devel at common-lisp.net > http://common-lisp.net/mailman/listinfo/elephant-devel From jingtaozf at gmail.com Fri Sep 24 07:02:08 2010 From: jingtaozf at gmail.com (Xu Jingtao) Date: Fri, 24 Sep 2010 15:02:08 +0800 Subject: [elephant-devel] elephant 1.0 is unstable under Clozure Common Lisp Version 1.5-r13651 (LinuxX8632) In-Reply-To: References: <4c9c3d53.013f970a.75cb.5b48@mx.google.com> Message-ID: <20100924.150208.153127167.jingtaozf@gmail.com> I have tried ccl 1.4 and it seems working fine. thanks very much. jingtao. eslick> eslick> Did you have this problem in 1.4? We use Elephant extensively on Clozure on Mac/Linux under 1.4 but I haven't upgraded to the latest 1.5 on any system that I'm aware of. There are some occasional bugs found in the schema management code too that may be lurk From jingtaozf at gmail.com Fri Sep 24 14:17:53 2010 From: jingtaozf at gmail.com (Xu Jingtao) Date: Fri, 24 Sep 2010 22:17:53 +0800 Subject: [elephant-devel] elephant 1.0 is unstable under Clozure Common Lisp Version 1.5-r13651 (LinuxX8632) In-Reply-To: References: <4c9c3d53.013f970a.75cb.5b48@mx.google.com> Message-ID: <4c9cb322.c971df0a.1cf2.3475@mx.google.com> hi eslick: This problem will also occure in 1.4,but not so often. If i try my operation one or two times,the operation will work fine again. eslick> Did you have this problem in 1.4? We use Elephant extensively on Clozure on Mac/Linux under 1.4 but I haven't upgraded to the latest 1.5 on any system that I'm aware of. There are some occasional bugs found in the schema management code too that may be lurking. eslick> eslick> Ian eslick> eslick> On Sep 23, 2010, at 10:51 PM, Xu Jingtao wrote: eslick> eslick> > hi elephant-dev: eslick> > I use elephant 1.0 under Clozure Common lisp,and exception often occurs eslick> > like this: eslick> > =============================================== eslick> > There is no applicable method for the generic function: eslick> > # eslick> > when called with arguments: eslick> > (NIL) eslick> > (B2D527D4) : 0 (PRINT-CALL-HISTORY :CONTEXT NIL :PROCESS NIL :ORIGIN NIL :DETAILED-P NIL :COUNT 536870911 :START-FRAME-NUMBER 0 :STREAM # :PRINT-LEVEL 2 :PRINT-LENGTH 5 :SHOW-INTERNAL-FRAMES NIL :FORMAT :TRADITIONAL) 735 eslick> > (B2D52888) : 1 (PRINT-BACKTRACE-TO-STREAM #) 71 eslick> > (B2D528A0) : 2 (GET-BACKTRACE) 327 eslick> > (B2D528D4) : 3 (FUNCALL #'#<(:INTERNAL (HUNCHENTOOT:HANDLE-REQUEST (HUNCHENTOOT:ACCEPTOR HUNCHENTOOT:REQUEST)))> #) 119 eslick> > (B2D528F0) : 4 (SIGNAL #) 903 eslick> > (B2D52918) : 5 (SIGNAL #) 903 eslick> > (B2D52940) : 6 (%ERROR # NIL -323663258) 119 eslick> > (B2D52954) : 7 (CERROR "Try calling it again" "There is no applicable method for the generic function:~% ~s~%when called with arguments:~% ~s" # (NIL)) 823 eslick> > (B2D52998) : 8 (FUNCALL #'#<#> # NIL) 103 eslick> > (B2D529B8) : 9 (FUNCALL #'#<#> # NIL NIL NIL) 199 eslick> > (B2D529E4) : 10 (%%STANDARD-COMBINED-METHOD-DCODE (# #) -323663226) 679 eslick> > (B2D52A2C) : 11 (UPDATE-OBSOLETE-INSTANCE #) 2359 eslick> > (B2D52A44) : 12 (%%NTH-ARG-DCODE #((#<#> #<#> #<#>) NIL NIL 1 # ...) -323663203) 1415 eslick> > (B2D52A80) : 13 (FUNCALL #'#<#> # 402 NIL) 223 eslick> > (B2D52A98) : 14 (FUNCALL #'#<#> # 402) 95 eslick> > (B2D52AAC) : 15 (FUNCALL #'#<#> # 308 NIL) 743 eslick> > (B2D52AF8) : 16 (FUNCALL #'#<(:INTERNAL ELEPHANT::MAP-OBJ ELEPHANT:MAP-INVERTED-INDEX)> "test at gmail.com" 308) 47 eslick> > (B2D52B10) : 17 (FUNCALL #'#<(:INTERNAL #:G18136 ELEPHANT::MAP-BTREE-VALUES)> "test at gmail.com" 308) 39 eslick> > (B2D52B28) : 18 (FUNCALL #'#<(:INTERNAL ELEPHANT::MAP-BTREE-VALUES)>) 519 eslick> > (B2D52B88) : 19 (FUNCALL #'#<#> # # :TRANSACTION NIL :PARENT NIL :ENVIRONMENT NIL :RETRIES 200 :RETRY-WAIT 0.1 :DEGREE-2 T :READ-UNCOMMITTED NIL :TXN-NOSYNC NIL :TXN-NOWAIT NIL :TXN-SYNC NIL :SNAPSHOT NIL :INHIBIT-ROLLBACK-FN NIL) 1351 eslick> > (B2D52C5C) : 20 (MAP-BTREE-VALUES # # "test at gmail.com" T) 719 eslick> > (B2D52C90) : 21 (FUNCALL #'#<#> eslick> > # # :VALUE "test at gmail.com" :COLLECT T) 183 eslick> > (B2D52CD0) : 22 (MAP-INVERTED-INDEX # # XJT-SITE::USER-MAIL :VALUE "test at gmail.com" :COLLECT T) 799 eslick> > (B2D52D2C) : 23 (url=/license/user-center) 119 eslick> > =============================================== eslick> > eslick> > I can retry my operation and the error will not occur the next time. From marc.daya at gmail.com Wed Sep 29 05:47:44 2010 From: marc.daya at gmail.com (marc daya) Date: Wed, 29 Sep 2010 07:47:44 +0200 Subject: [elephant-devel] deserialization error on (make-pset) Message-ID: Greetings I've run into a problem on the latest Elephant 1.0 from the darcs repository, with SBCL 1.0.34 on FreeBSD and 1.0.39 on MacOS. (make-pset) fails with a deserialization error (steps below). Other operations like creating and initializing a persistent class, or adding to the root, work fine. Am I doing something silly? .marc --- (steps to reproduce follow) --- * (in-package :ele-user) # * (open-store '(:bdb #P"/tmp/tmpstore")) ; loading system definition from ... ... ; ; compilation unit finished ; printed 197 notes # * (make-pset) debugger invoked on a ELEPHANT-DESERIALIZATION-ERROR in thread #: Elephant deserialization error: When attempting to set the slot's value to ELEPHANT::SUCCESSOR (SETF of SLOT-VALUE), the slot NIL (A UNBOUND-SLOT was caught when trying to print SB-DEBUG:*DEBUG-CONDITION* when entering the debugger. Printing was aborted and the UNBOUND-SLOT was stored in SB-DEBUG::*NESTED-DEBUG-CONDITION*.) (CELL-ERROR-NAME SB-DEBUG::*NESTED-DEBUG-CONDITION*) = ELEPHANT::CLASSNAME Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (ELEPHANT::DESERIALIZE #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER # :SIZE 822 :POSITION 653 :LENGTH 1184) # NIL) -- Never have so many understood so little about so much. ? ? ? ? ? ? ? ?-- James Burke From marc.daya at gmail.com Thu Sep 30 08:09:34 2010 From: marc.daya at gmail.com (marc daya) Date: Thu, 30 Sep 2010 10:09:34 +0200 Subject: [elephant-devel] deserialization error on (make-pset) In-Reply-To: References: Message-ID: On 29 September 2010 07:47, marc daya wrote: > I've run into a problem on the latest Elephant 1.0 from the darcs > repository, with SBCL 1.0.34 on FreeBSD and 1.0.39 on MacOS. > (make-pset) fails with a deserialization error (steps below). ?Other > operations like creating and initializing a persistent class, or > adding to the root, work fine. ?Am I doing something silly? I was doing something silly. It seems that I somehow managed to get my systems into a state where the fasls and shared libs were out of sync. After a complete clean and rebuild everything works as expected. I'm sorry if I wasted anyone's time with this. .marc -- Never have so many understood so little about so much. ? ? ? ? ? ? ? ?-- James Burke