RE: Using CommonCrawl for POI regression-mass-testing

Sweet! Please feel free to make any use that you can out of [0]. Y, I’m storing results in a db as well (h2) and using that to dump reports along the lines of [1]…note I’m using POI to generate xlsx files now ☺. Is there any way we could collaborate on the eval code? My active dev (when I

[Bug 58858] New: hidden characters not removed

https://bz.apache.org/bugzilla/show_bug.cgi?id=58858 Bug ID: 58858 Summary: hidden characters not removed Product: POI Version: unspecified Hardware: PC Status: NEW Severity: critical Priority: P2

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 --- Comment #6 from Nick Burch --- For the HSSF stuff, look at FeatFormulaErr2 Looks at first glance like the list is almost the same. Assuming that's really the case, it'd probably be best to put the IgnoredErrorType

[Bug 56892] [PATCH] Ignoring number-stored-as-text warnings requires going via CTWorksheet

https://bz.apache.org/bugzilla/show_bug.cgi?id=56892 Dominik Stadler changed: What|Removed |Added Severity|normal |enhancement

Re: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

Yes, it seems there is no easy way to set a higher timeout per project, see e.g. https :// issues.apache.org

[Bug 53207] A formula can not clear by [setCellFormula(null)] in Shared　formulas.

https://bz.apache.org/bugzilla/show_bug.cgi?id=53207 ki changed: What|Removed |Added CC||tersit...@gmail.com -- You

[Bug 58869] New: when use setCellFormula change the cells with shared fomulas

https://bz.apache.org/bugzilla/show_bug.cgi?id=58869 Bug ID: 58869 Summary: when use setCellFormula change the cells with shared fomulas Product: POI Version: 3.12-FINAL Hardware: PC Status: NEW

Re: Using CommonCrawl for POI regression-mass-testing

Hi, wow, nice slides! I am not working as sophisticated as you on this one, but rather focused on finding regressions and catastrophic failures of POI for now, because the large number of failures is hard to sort into actual failures and other things. I think one of the next steps will be to

[GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project ooxml-schemas has an issue affecting its community integration. This

Re: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

Maybe its possible to split the compilation in smaller parts and reference the already compiled schema, i.e. something like in [1] I guess this would lead to a faster compilation with a smaller memory footprint. ... and of course this would fit with my plan to have separate modules/schema jars :)

Re: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed

The important line here is The current state of this project is 'Failed', with reason 'Build Timed Out'. So there is a time-limit on jobs on Gump which we sometimes exceed. We get this now because I added the correct email-recipients to the Gump setup lately. Seems like the build-machine is