This looks good. I pushed it to elephant-unstable.
I wonder if the same problem will occur with the other backends and
whether there is a common patch we might apply? Has anyone tried
upgrading from 0.9.1 or an earlier release to elephant-unstable?
Thanks,
Ian
On Jan 2, 2009, at 8:15 AM, q
pushed. -Ian
On Jan 1, 2009, at 8:31 AM, quan hu wrote:
> Hi Ian,
>
> For the pathname fix, I attached the patch.
>
> For the 0.9.1 upgrade fix, I got one failure and one
> successful result.
> I need to double check if the failure is caused by my test
> execution step or oth
Great, thank you! I'll check this in later today.
Ian
Sent from my iPhone
On Jan 1, 2009, at 8:31 AM, "quan hu" wrote:
Hi Ian,
For the pathname fix, I attached the patch.
For the 0.9.1 upgrade fix, I got one failure and one
successful result.
I need to double check if th
Hi Ian,
For the pathname fix, I attached the patch.
For the 0.9.1 upgrade fix, I got one failure and one successful
result.
I need to double check if the failure is caused by my test execution
step or other issue.
I'll send the result later.
Thanks
Quan
2008/12/31 Ian Esli
I don't think we've tried the upgrade procedure in awhile, so it's
possible an incompatibility slipped in. It may be that all you need
to do is make sure that defaults are properly created for slot values
that are unbound during the store controller opening phase.
Adding a case for pathname
Hi Ian,
I downloaded the patches and have more testing today. The lock issue is
gone!
Thanks a lot.
1. But, another issue is found. migrate pathname fails. I test it under
SBCL 1.0.21
e.g.
> (migrate *store-controller* #p"/tmp) => Error: Cannot migrate
function object
Hi Quan,
Thank you again for the information on this bug. The short story is
that the way we are keeping track of transactions assumed that there
were only two stores in the nested transaction stack (outer and
inner). Migrating a nested object inside a with-transaction would not
pass the
This scenario worked for migration as of the last release so a bug
must have
crept in with the new features. Thank you for the investigation, it
only works if you are very careful. There should be some info on this
in the txn src code or in the manual - I'll look into this when I can
if
Hello,
After more investigation, here are some suspects:
In the current elephant codes, the macro my-current-transaction will
check if the current transaction belongs to the sc parameter. If not, just
return +NULL-CHAR+. That's exactly the case in the following nested
transaction wh
Hi Ian, Yarek,
Thanks for providing the information.
I downloaded the elephant-unstable and test it with BDB4.7.
The failure symptom is the same: target store controller get locked.
After I make following changes in migrate.lisp; The test passed.
(defmethod copy-btree-co
Quan,
Unstable is here:
http://www.common-lisp.net/project/elephant/darcs/elephant-unstable
Yarek
On Mon, Dec 29, 2008 at 5:37 AM, Ian Eslick wrote:
> That would be elephant-unstable
>
> Sent from my iPhone
>
> On Dec 29, 2008, at 7:36 AM, Ian Eslick wrote:
>
> > Hi Quan,
> >
> > Can you tr
That would be elephant-unstable
Sent from my iPhone
On Dec 29, 2008, at 7:36 AM, Ian Eslick wrote:
> Hi Quan,
>
> Can you try the latest darcs with BDB 4.6 or 4.7? I made some changes
> to migration, but I can't recall if they were in the latest darcs or
> not - I think the latest darcs doesn'
Hi Quan,
Can you try the latest darcs with BDB 4.6 or 4.7? I made some changes
to migration, but I can't recall if they were in the latest darcs or
not - I think the latest darcs doesn't play well with BDB 4.5 so
please make sure you can reproduce under the above configuration if
you can.
13 matches
Mail list logo
