[Bug 62993] SUMIF returns wrong result (POI 4.0.x)

2019-01-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62993 gallon.fi...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 62993] SUMIF returns wrong result (POI 4.0.x)

2018-12-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62993 Axel Howind changed: What|Removed |Added OS|Mac OS X 10.1 |All Hardware|PC

[Bug 62993] SUMIF returns wrong result (POI 4.0.x)

2018-12-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62993 Axel Howind changed: What|Removed |Added Attachment #36313|0 |1 is obsolete|

[Bug 62993] SUMIF returns wrong result (POI 4.0.x)

2018-12-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62993 --- Comment #4 from Axel Howind --- Sorry, it seems this patch introduces a regression that I didn't see because Junit was broken on my machine (I opened Bug 62996 for that problem). Now that Junit is up and running again, I will look into the

[Bug 62993] SUMIF returns wrong result (POI 4.0.x)

2018-12-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62993 --- Comment #3 from Axel Howind --- Created attachment 36315 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36315=edit Patch that fixes bug 62993 Patch to fix Bug 62993 `XSSFEvaluationSheet` uses an internal cache to speed up

[Bug 62993] SUMIF returns wrong result (POI 4.0.x)

2018-12-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62993 --- Comment #2 from Axel Howind --- It turns out that this probably not only affects SUMIF but possibly all functions that operate on ranges. Bug is triggered when rows are added after the first formula evaluation is done. I have prepared a

[Bug 62993] SUMIF returns wrong result (POI 4.0.x)

2018-12-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62993 --- Comment #1 from Axel Howind --- Created attachment 36313 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36313=edit JUnit test for this The attachment contains a JUnit test case for this bug. I am unsure where this should end up in