[Erp5-dev] Delayed reindex, workflow script and acquisition

bartek bartek at gorny.edu.pl
Sat Nov 13 23:18:14 CET 2010


On Sat, 13 Nov 2010 23:30:25 +0900
Nicolas Dumazet <nicolas.dumazet at nexedi.com> wrote:

> On 11/13/2010 06:20 PM, Bartek Górny wrote:
> > This goes back to my other email - the test to show the problem
> > would be like:
> > 
> > doSomething
> > doAnotherThing
> > self.tic()
> > check
> 
> Hello Bartek.
> 
> You seemed to care quite a lot about this issue in your previous
> emails. From what I understand, you know enough of ERP5 to turns this
> into a successful bug report.
> I'm sure that you can afford to spend some more time on the diagnosis,
> to prove us, with a complete TestCase, that something _is_ indeed
> broken :)

Unfortunately, I can't. I've already spent enough time on
it. What I'm writing about is an observation from a real-life
installation. I know enough about ERP5 to tell you exactly what
happens, when it happens, where it happens, to tell you how to
reproduce the problem, and to formulate a hypothesis why it may happen.
That's basically what a bug report is supposed to contain. What you are
going to do with it is up to you.

See, I'm not lobbying for a feature request; I'm not asking you to do
anything for me or for anybody. I'm warning you there might be a serious
flaw in the core which in some circumstances can bring disaster. If
I'm wrong, that'd be perfect - though I'd be more comfortable if
somebody "from upstream" actually proved me wrong. If you don't care, or
if you are so convinced that everything is perfect that you don't even
need to check, good for you.

Bartek

> 
> Regards,
> 
> > 
> > to show what happens if "another thing" is done before the
> > activities go through. I don't know any other way to reproduce this
> > problem in tests.
> > 
> > Bartek
> 
> 




More information about the Erp5-dev mailing list