On Fri, Sep 18, 2009 at 09:51, Martin Langhoff
wrote:
> On Fri, Sep 18, 2009 at 2:10 AM, James Cameron wrote:
>> By branching at the 0.82 point as deployed, determining from evidence
>
> Good theoretical re-statement. You post may clarify things for other
> readers -- as for me, I know very well
On Fri, Sep 18, 2009 at 12:32:49PM +0200, Tomeu Vizoso wrote:
> On Fri, Sep 18, 2009 at 12:26, James Cameron wrote:
> > And just a question on Ivan's try/except patch that is so effective in
> > 0.82 in allowing a child to continue using the system with a fresh
> > journal ... would it be true to
On Fri, Sep 18, 2009 at 12:26 PM, James Cameron wrote:
> And just a question on Ivan's try/except patch that is so effective in
> 0.82 in allowing a child to continue using the system with a fresh
> journal ... would it be true to say that this also hides the cause of
> the failure to open the jou
On Fri, Sep 18, 2009 at 12:26, James Cameron wrote:
> And just a question on Ivan's try/except patch that is so effective in
> 0.82 in allowing a child to continue using the system with a fresh
> journal ... would it be true to say that this also hides the cause of
> the failure to open the journa
And just a question on Ivan's try/except patch that is so effective in
0.82 in allowing a child to continue using the system with a fresh
journal ... would it be true to say that this also hides the cause of
the failure to open the journal, and so any system with a renamed
datastore would not have
On Fri, Sep 18, 2009 at 11:47:59AM +0200, Martin Langhoff wrote:
> We can offer the patch to deployers, and I can integrate it into a
> build. But our reach is limited there. A user-deployable "repair" tool
> is a lot more effective.
Hmm. Yes, I can see that it would be, given the deployment cons
Hi all,
Sorry for not being in the thread,
its 0.86 release time..
On Thu, Sep 17, 2009 at 11:37:04AM +0200, Martin Langhoff wrote:
> Welcome new maintainer!
>
> I am currently doing a bit of work with LatAm deployments, so I do
> have some notes related to DS. You may be aware of these issues,
On Fri, Sep 18, 2009 at 02:10, James Cameron wrote:
> On Thu, Sep 17, 2009 at 04:51:47PM +0200, Martin Langhoff wrote:
>> So I am strictly looking forward -- and wondering if we can help these
>> users of 0.82 now.
>
> By branching at the 0.82 point as deployed, determining from evidence
> (those
On Fri, Sep 18, 2009 at 11:34 AM, Tomeu Vizoso wrote:
> I agree that an activity for repairing or recovering the DS would be
> quite beneficial, we'd need to add an exception for Rainbow though.
So Rainbow would prevent a regular activity from reading .sugar? I am
not familiar with how one goes a
On Thu, Sep 17, 2009 at 16:51, Martin Langhoff
wrote:
> On Thu, Sep 17, 2009 at 4:27 PM, Gary C Martin wrote:
>> FWIW, your three major points were fixed way back by Tomeu's 0.84 data-store
>> re-write to make for robustness. Actually I'm fairly sure it was these
>> kind'a reports that prompted T
On Thu, Sep 17, 2009 at 11:37, Martin Langhoff
wrote:
> Welcome new maintainer!
>
> I am currently doing a bit of work with LatAm deployments, so I do
> have some notes related to DS. You may be aware of these issues, of
> course.
>
> - "Dataloss" on startup. We are hearing of some issues in the
On Fri, Sep 18, 2009 at 11:15:17AM +0200, Martin Langhoff wrote:
> On Fri, Sep 18, 2009 at 10:58 AM, James Cameron wrote:
> > I can't find any evidence that this logic has been retained ... looked
> > in git://git.sugarlabs.org/sugar/mainline.git and
> > git://git.sugarlabs.org/sugar-datastore/mai
On Fri, Sep 18, 2009 at 10:58 AM, James Cameron wrote:
> I can't find any evidence that this logic has been retained ... looked
> in git://git.sugarlabs.org/sugar/mainline.git and
> git://git.sugarlabs.org/sugar-datastore/mainline.git
Well, this sounds promising-- but I am definitely not familiar
On Fri, Sep 18, 2009 at 09:51:58AM +0200, Martin Langhoff wrote:
> And here you can find "steps to repro" and a workaround if you want to
> see it in action:
>
> http://dev.laptop.org/ticket/7719
Thanks. I shall look there for an exception.
> As for the code that controls this?
> in shell/vie
On Fri, Sep 18, 2009 at 2:10 AM, James Cameron wrote:
> By branching at the 0.82 point as deployed, determining from evidence
Good theoretical re-statement. You post may clarify things for other
readers -- as for me, I know very well what I am requesting. And I do
respect that it is not easy.
It
On Thu, Sep 17, 2009 at 04:51:47PM +0200, Martin Langhoff wrote:
> So I am strictly looking forward -- and wondering if we can help these
> users of 0.82 now.
By branching at the 0.82 point as deployed, determining from evidence
(those renamed DS directories you have been unable to obtain) what th
On Thu, Sep 17, 2009 at 4:27 PM, Gary C Martin wrote:
> FWIW, your three major points were fixed way back by Tomeu's 0.84 data-store
> re-write to make for robustness. Actually I'm fairly sure it was these
> kind'a reports that prompted Tomeu to make that fine effort. Prior to this
> (0.82) I had
Hi Martin,
FWIW, your three major points were fixed way back by Tomeu's 0.84 data-
store re-write to make for robustness. Actually I'm fairly sure it was
these kind'a reports that prompted Tomeu to make that fine effort.
Prior to this (0.82) I had seen occasional datastore 'loss', sometime
Welcome new maintainer!
I am currently doing a bit of work with LatAm deployments, so I do
have some notes related to DS. You may be aware of these issues, of
course.
- "Dataloss" on startup. We are hearing of some issues in the field
with "dataloss" -- not real dataloss but if there is anything
On Wed, Sep 16, 2009 at 03:55:07PM -0500, David Farning wrote:
Great job and congrats on handing off the modules and a heartfelt
thanks to alsroot and Benjamin Berg for pick them up.
+1
CU Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
signature.asc
Description: Digital signat
Great job and congrats on handing off the modules and a heartfelt
thanks to alsroot and Benjamin Berg for pick them up.
david
On Wed, Sep 16, 2009 at 10:07 AM, Tomeu Vizoso wrote:
> Hi,
>
> the other day I passed maintenance of the Journal and the Datastore to
> Aleksey, who has been doing alrea
Hi,
the other day I passed maintenance of the Journal and the Datastore to
Aleksey, who has been doing already a great job at helping with new
features, bug fixes, design discussions and all the rest of what makes
a maintainer.
But I would like to warn that Aleksey codes very fast and lives very
22 matches
Mail list logo
