<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - - sporadic fail! - combination of autocalculate and shared formulae still broken in 6.3.0.0.alpha1+ with threaded off" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125320#c33">Comment # 33</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - - sporadic fail! - combination of autocalculate and shared formulae still broken in 6.3.0.0.alpha1+ with threaded off" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125320">bug 125320</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>You may continue here.. but devs like 'really' concrete issues. (In reply to matthewnote from <a href="show_bug.cgi?id=125320#c31">comment #31</a>) > > * The problem is hard to reproduce. That's unfortunate, but Calc is a > > complex piece of software > > Careful. We know that, appreciate it and deploy it with much enthusiasm. > > > I'm setting this bugreport to NEEDINFO. > > > A large number of comments here are vague descriptions of problems with Calc > > calculating something incorrectly that may not have to do anything with this > > bugreport besides sharing the pattern of something not getting calculated > > correctly. > > Incorrect. Precise example given. A Bug that prevents bug reporting is the > subject. > > Mixing several different problems in one bugreport only makes it > > more difficult and confusing to handle, and so they do not belong here. > > It clarifies (according to b, who saw the point . . .immediately). > "Sporadic fails" is the first point in the/his title. Evidence belongs here > for the moment - according to his (vast) user experience. > Luboš Luňák is a developer who mostly handling this type of calculation issues.. However, as most developers.. the prefer clear specification of the issue. So something where they can work with. Until then the are not supposed to be contacted (as general rule). Arguing with them pointless. And the don't figure causes.. The only want to now to route to current result and and the expected one. This bug is ruined as bug report - dedicated to developers. The don't like long reads. And unclear steps. A certainly not both at the same time.. >From QA level I would say, keeping this thing alive being fine.. until we actually catch something.. create fresh report with that.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>