> I've noticed some of that stuff going on in elephant-unstable and
> haven't been able to track it down yet. I'm surprised to hear it's in
> stable... Any hints as to what kind of data this is failing on?
To find the cause of this it would probably be beneficial
to perform the split from the %
And here's a backtrace.
0: (DESERIALIZE
#S(ELEPHANT-MEMUTIL:BUFFER-STREAM
:BUFFER #
:SIZE 39
:POSITION 39
:LENGTH 163845)
#)
1: (DB-POSTMODERN::DESERIALIZE-FROM-DATABASE
#(15 226 27 0 0 13 9 9 0 0 0 73 ...)
#)
2: ((SB-PCL::FAST-METHOD DB-POSTMODERN::CUR
> I've noticed some of that stuff going on in elephant-unstable and
> haven't been able to track it down yet. I'm surprised to hear it's in
> stable... Any hints as to what kind of data this is failing on?
Reproduce using test suite:
* load elephant-tests, set up backend tests (I was using th
LPP> Clues?
just a guess -- after re-loading some stuff (such as defconstant and
defparameter definitions)
will be re-created and won't be EQL to previous versions, so comparisons
might fail.
___
elephant-devel site list
elephant-devel@common-lisp.
I've noticed some of that stuff going on in elephant-unstable and
haven't been able to track it down yet. I'm surprised to hear it's in
stable... Any hints as to what kind of data this is failing on?
Ian
On Jul 24, 2008, at 10:42 AM, Leslie P. Polzer wrote:
When I reload the Elephant-sta
When I reload the Elephant-stable ASDF system
in a live environment with open store controller,
I pretty reliably get non-specific deserialization errors.
Clues?
Leslie
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.ne
