Re: Is it time for POI 3.17-beta1?

[Greg Woolsey]

The example file with AlternateContent wrappers for table element styles is
handled correctly now by r1799733 and added as a unit test.  Existing tests
still pass for me, plus my own downstream integrations.

On Fri, Jun 23, 2017 at 1:07 PM Greg Woolsey  wrote:

> I checked in the units merge this morning.  I'll dig more into what
> drawing does for alternate content.
>
> On Fri, Jun 23, 2017, 12:57 Andreas Beeker  wrote:
>
>> AlternateContent is also used in XSLF and XmlBeans provides either a
>> XPath or a Cursor API,
>> to access those - just have a look at XSLFDrawing - if you need help, I
>> can support.
>>
>> So I'm waiting for your modifications (+EMUUtils merge), before preparing
>> the release candidate.
>>
>> Andi
>>
>> On 6/23/17 8:44 PM, Greg Woolsey wrote:
>> > In this particular case, the test file defines "mc:AlternateContent" for
>> > some table styles.  I've not played around with those, and the few
>> cases I
>> > see already in POI seem pretty specific to those areas of content.
>> >
>> > Anyone have strong opinions on whether XSSFTableStyle should do anything
>> > with these?  If so, anyone have experience with XMLBeans in the context
>> of
>> > finding and parsing sub-elements into CT* beans?
>> >
>> > My initial reaction is that this is a lightly used area and specific to
>> 3rd
>> > party implementations of OOXML with custom extensions, so doing nothing
>> > beyond gracefully ignoring these is a viable option for now.
>> >
>> > On Fri, Jun 23, 2017 at 10:02 AM Greg Woolsey 
>> > wrote:
>> >
>> >> I'll take a look at that exception, I touched XSSFTableStyle.
>>
>>
>>

Re: Is it time for POI 3.17-beta1?

[Greg Woolsey]

I checked in the units merge this morning.  I'll dig more into what drawing
does for alternate content.

On Fri, Jun 23, 2017, 12:57 Andreas Beeker  wrote:

> AlternateContent is also used in XSLF and XmlBeans provides either a XPath
> or a Cursor API,
> to access those - just have a look at XSLFDrawing - if you need help, I
> can support.
>
> So I'm waiting for your modifications (+EMUUtils merge), before preparing
> the release candidate.
>
> Andi
>
> On 6/23/17 8:44 PM, Greg Woolsey wrote:
> > In this particular case, the test file defines "mc:AlternateContent" for
> > some table styles.  I've not played around with those, and the few cases
> I
> > see already in POI seem pretty specific to those areas of content.
> >
> > Anyone have strong opinions on whether XSSFTableStyle should do anything
> > with these?  If so, anyone have experience with XMLBeans in the context
> of
> > finding and parsing sub-elements into CT* beans?
> >
> > My initial reaction is that this is a lightly used area and specific to
> 3rd
> > party implementations of OOXML with custom extensions, so doing nothing
> > beyond gracefully ignoring these is a viable option for now.
> >
> > On Fri, Jun 23, 2017 at 10:02 AM Greg Woolsey 
> > wrote:
> >
> >> I'll take a look at that exception, I touched XSSFTableStyle.
>
>
>

Re: Is it time for POI 3.17-beta1?

[Andreas Beeker]

AlternateContent is also used in XSLF and XmlBeans provides either a XPath or a 
Cursor API,
to access those - just have a look at XSLFDrawing - if you need help, I can 
support.

So I'm waiting for your modifications (+EMUUtils merge), before preparing the 
release candidate.

Andi

On 6/23/17 8:44 PM, Greg Woolsey wrote:
> In this particular case, the test file defines "mc:AlternateContent" for
> some table styles.  I've not played around with those, and the few cases I
> see already in POI seem pretty specific to those areas of content.
>
> Anyone have strong opinions on whether XSSFTableStyle should do anything
> with these?  If so, anyone have experience with XMLBeans in the context of
> finding and parsing sub-elements into CT* beans?
>
> My initial reaction is that this is a lightly used area and specific to 3rd
> party implementations of OOXML with custom extensions, so doing nothing
> beyond gracefully ignoring these is a viable option for now.
>
> On Fri, Jun 23, 2017 at 10:02 AM Greg Woolsey 
> wrote:
>
>> I'll take a look at that exception, I touched XSSFTableStyle.




signature.asc
Description: OpenPGP digital signature

Re: Is it time for POI 3.17-beta1?

[Greg Woolsey]

In this particular case, the test file defines "mc:AlternateContent" for
some table styles.  I've not played around with those, and the few cases I
see already in POI seem pretty specific to those areas of content.

Anyone have strong opinions on whether XSSFTableStyle should do anything
with these?  If so, anyone have experience with XMLBeans in the context of
finding and parsing sub-elements into CT* beans?

My initial reaction is that this is a lightly used area and specific to 3rd
party implementations of OOXML with custom extensions, so doing nothing
beyond gracefully ignoring these is a viable option for now.

On Fri, Jun 23, 2017 at 10:02 AM Greg Woolsey <greg.wool...@gmail.com>
wrote:

> I'll take a look at that exception, I touched XSSFTableStyle.
>
> On Fri, Jun 23, 2017, 09:14 Allison, Timothy B. <talli...@mitre.org>
> wrote:
>
>> My run just finished as well.
>>
>> http://162.242.228.174/reports/reports_poi-3.17-beta1.zip
>>
>> +1 to roll
>>
>> I get only one new exception (below) in an xlsx file (there are 7 new
>> zlib/gzip in embedded files) and roughly 200 fixed exceptions (mostly wmf)
>> (see: exceptions/new_exceptions_in_B_by_mime.xlsx,
>> exceptions/fixed_exceptions_in_B_by_mime.xlsx)
>>
>> There appear to be pretty sizable improvements in the common tokens
>> metric...I saw with caveats...
>> ("content/common_token_comparisons_by_mime.xlsx")
>>
>> I don't see any major red flags in the content diffs
>> ("content/content_diffs_ignore_exceptions.xlsx")
>>
>> The one new exception in xlsx:
>>
>> http://162.242.228.174/docs/commoncrawl2_extras/xlsx/NL/NLBOF7IUZGMNKT3KJSXSQIQYPXOSH3TO
>>
>> ArrayIndexOutOfBounds
>> at
>> org.openxmlformats.schemas.spreadsheetml.x2006.main.impl.CTDxfsImpl.getDxfArray(Unknown
>> Source)
>> at
>> org.apache.poi.xssf.usermodel.XSSFTableStyle.(XSSFTableStyle.java
>> at
>> org.apache.poi.xssf.model.StylesTable.readFrom(StylesTable.java:247)
>> at
>> org.apache.poi.xssf.model.StylesTable.(StylesTable.java:141)
>> at
>> org.apache.poi.xssf.eventusermodel.XSSFReader.getStylesTable(XSSFReader.java:127)
>> at
>> o.a.t.parser.microsoft.ooxml.XSSFExcelExtractorDecorator.buildXHTML(XSSFExcelExtractorDecorator.java:130)
>>
>> -Original Message-
>> From: Dominik Stadler [mailto:dominik.stad...@gmx.at]
>> Sent: Friday, June 23, 2017 6:02 AM
>> To: POI Developers List <dev@poi.apache.org>
>> Subject: Re: Is it time for POI 3.17-beta1?
>>
>> Hi,
>>
>> The 6 errors about password are actually something that I should handle
>> differently in the test-framework and is easily fixed there, so only the
>> one single failure in drawing slides remains, very nice indeed!
>>
>> Dominik.
>>
>> On Fri, Jun 23, 2017 at 11:05 AM, Dominik Stadler <dominik.stad...@gmx.at
>> >
>> wrote:
>>
>> > Hi,
>> >
>> > Mass testing results are in and look quite good. Out of 1066412
>> > documents,
>> > 136777 are detected as invalid, 76768 cause an error, error rate is
>> > 7.2% compared to 7.17% in 3.16 and 7.13% in 3.15, however we do much
>> > more checks over time, which hopefully explains the slight increase.
>> >
>> > Compared to 3.16 only 7 new errors were seen, 6 of those are related
>> > to invalid password being set (probably due to more testing now) and 1
>> > related to drawing slides.
>> >
>> > o.a.p.EncryptedDocumentException: o.a.p.EncryptedDocumentException:
>> Invalid password specified - use
>> Biff8EncryptionKey.setCurrentUserPassword() before calling extractor
>> >   at
>> o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:429)
>> >   at
>> o.a.p.extractor.ExtractorFactory.createExtractor(ExtractorFactory.java:135)
>> >   at
>> o.a.p.stress.AbstractFileHandler.handleExtractingInternal(AbstractFileHandler.java:88)
>> >   at
>> > o.a.p.stress.AbstractFileHandler.handleExtracting(AbstractFileHandler.
>> > java:63) Caused by: o.a.p.EncryptedDocumentException: Invalid password
>> > specified - use Biff8EncryptionKey.setCurrentUserPassword() before
>> calling extractor
>> >   at
>> o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:422)
>> >   ... 10 more
>> >
>> > java.lang.IllegalArgumentException: Start point cannot equalendpoint
>> >   at java.awt.LinearGradientPaint.(LinearGradie

Re: Is it time for POI 3.17-beta1?

[Greg Woolsey]

I'll take a look at that exception, I touched XSSFTableStyle.

On Fri, Jun 23, 2017, 09:14 Allison, Timothy B. <talli...@mitre.org> wrote:

> My run just finished as well.
>
> http://162.242.228.174/reports/reports_poi-3.17-beta1.zip
>
> +1 to roll
>
> I get only one new exception (below) in an xlsx file (there are 7 new
> zlib/gzip in embedded files) and roughly 200 fixed exceptions (mostly wmf)
> (see: exceptions/new_exceptions_in_B_by_mime.xlsx,
> exceptions/fixed_exceptions_in_B_by_mime.xlsx)
>
> There appear to be pretty sizable improvements in the common tokens
> metric...I saw with caveats...
> ("content/common_token_comparisons_by_mime.xlsx")
>
> I don't see any major red flags in the content diffs
> ("content/content_diffs_ignore_exceptions.xlsx")
>
> The one new exception in xlsx:
>
> http://162.242.228.174/docs/commoncrawl2_extras/xlsx/NL/NLBOF7IUZGMNKT3KJSXSQIQYPXOSH3TO
>
> ArrayIndexOutOfBounds
> at
> org.openxmlformats.schemas.spreadsheetml.x2006.main.impl.CTDxfsImpl.getDxfArray(Unknown
> Source)
> at
> org.apache.poi.xssf.usermodel.XSSFTableStyle.(XSSFTableStyle.java
> at
> org.apache.poi.xssf.model.StylesTable.readFrom(StylesTable.java:247)
> at
> org.apache.poi.xssf.model.StylesTable.(StylesTable.java:141)
> at
> org.apache.poi.xssf.eventusermodel.XSSFReader.getStylesTable(XSSFReader.java:127)
> at
> o.a.t.parser.microsoft.ooxml.XSSFExcelExtractorDecorator.buildXHTML(XSSFExcelExtractorDecorator.java:130)
>
> -Original Message-
> From: Dominik Stadler [mailto:dominik.stad...@gmx.at]
> Sent: Friday, June 23, 2017 6:02 AM
> To: POI Developers List <dev@poi.apache.org>
> Subject: Re: Is it time for POI 3.17-beta1?
>
> Hi,
>
> The 6 errors about password are actually something that I should handle
> differently in the test-framework and is easily fixed there, so only the
> one single failure in drawing slides remains, very nice indeed!
>
> Dominik.
>
> On Fri, Jun 23, 2017 at 11:05 AM, Dominik Stadler <dominik.stad...@gmx.at>
> wrote:
>
> > Hi,
> >
> > Mass testing results are in and look quite good. Out of 1066412
> > documents,
> > 136777 are detected as invalid, 76768 cause an error, error rate is
> > 7.2% compared to 7.17% in 3.16 and 7.13% in 3.15, however we do much
> > more checks over time, which hopefully explains the slight increase.
> >
> > Compared to 3.16 only 7 new errors were seen, 6 of those are related
> > to invalid password being set (probably due to more testing now) and 1
> > related to drawing slides.
> >
> > o.a.p.EncryptedDocumentException: o.a.p.EncryptedDocumentException:
> Invalid password specified - use
> Biff8EncryptionKey.setCurrentUserPassword() before calling extractor
> >   at
> o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:429)
> >   at
> o.a.p.extractor.ExtractorFactory.createExtractor(ExtractorFactory.java:135)
> >   at
> o.a.p.stress.AbstractFileHandler.handleExtractingInternal(AbstractFileHandler.java:88)
> >   at
> > o.a.p.stress.AbstractFileHandler.handleExtracting(AbstractFileHandler.
> > java:63) Caused by: o.a.p.EncryptedDocumentException: Invalid password
> > specified - use Biff8EncryptionKey.setCurrentUserPassword() before
> calling extractor
> >   at
> o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:422)
> >   ... 10 more
> >
> > java.lang.IllegalArgumentException: Start point cannot equalendpoint
> >   at java.awt.LinearGradientPaint.(LinearGradientPaint.java:295)
> >   at
> o.a.p.sl.draw.PathGradientPaint$PathGradientContext.(PathGradientPaint.java:104)
> >   at
> o.a.p.sl.draw.PathGradientPaint.createContext(PathGradientPaint.java:61)
> >   at
> sun.java2d.pipe.AlphaPaintPipe.startSequence(AlphaPaintPipe.java:84)
> >   at sun.java2d.pipe.AAShapePipe.renderTiles(AAShapePipe.java:168)
> >   at sun.java2d.pipe.AAShapePipe.renderPath(AAShapePipe.java:159)
> >   at sun.java2d.pipe.AAShapePipe.fill(AAShapePipe.java:68)
> >   at
> sun.java2d.pipe.PixelToParallelogramConverter.fill(PixelToParallelogramConverter.java:164)
> >   at sun.java2d.pipe.ValidatePipe.fill(ValidatePipe.java:160)
> >   at sun.java2d.SunGraphics2D.fill(SunGraphics2D.java:2527)
> >   at o.a.p.sl.draw.DrawSimpleShape.draw(DrawSimpleShape.java:89)
> >   at o.a.p.sl.draw.DrawGroupShape.draw(DrawGroupShape.java:60)
> >   at o.a.p.sl.draw.DrawSheet.draw(DrawSheet.java:71)
> >   at o.a.p.sl.draw.DrawSlide.draw(DrawSlide.java:4

RE: Is it time for POI 3.17-beta1?

[Allison, Timothy B.]

Thank you, Dominik!  Your reports are so much more easily navigable than mine...

I'll take a look at this one next week.  This is not a blocker.

Caused by: java.lang.ArrayIndexOutOfBoundsException: *
at 
o.a.p.util.LittleEndianCP950Reader.read(LittleEndianCP950Reader.java:77)
at o.a.p.util.CodePageUtil.cp950ToString(CodePageUtil.java:467)
at o.a.p.hwpf.model.TextPiece.buildInitSB(TextPiece.java:78)
at o.a.p.hwpf.model.TextPiece.(TextPiece.java:58)
at o.a.p.hwpf.HWPFOldDocument.buildTextPiece(HWPFOldDocument.java:182)
at o.a.p.hwpf.HWPFOldDocument.(HWPFOldDocument.java:113)



-Original Message-
From: Dominik Stadler [mailto:dominik.stad...@gmx.at] 
Sent: Friday, June 23, 2017 5:05 AM
To: POI Developers List <dev@poi.apache.org>
Subject: Re: Is it time for POI 3.17-beta1?

Hi,

Mass testing results are in and look quite good. Out of 1066412 documents,
136777 are detected as invalid, 76768 cause an error, error rate is 7.2% 
compared to 7.17% in 3.16 and 7.13% in 3.15, however we do much more checks 
over time, which hopefully explains the slight increase.

Compared to 3.16 only 7 new errors were seen, 6 of those are related to invalid 
password being set (probably due to more testing now) and 1 related to drawing 
slides.

o.a.p.EncryptedDocumentException: o.a.p.EncryptedDocumentException:
Invalid password specified - use
Biff8EncryptionKey.setCurrentUserPassword() before calling extractor
at 
o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:429)
at 
o.a.p.extractor.ExtractorFactory.createExtractor(ExtractorFactory.java:135)
at 
o.a.p.stress.AbstractFileHandler.handleExtractingInternal(AbstractFileHandler.java:88)
at 
o.a.p.stress.AbstractFileHandler.handleExtracting(AbstractFileHandler.java:63)
Caused by: o.a.p.EncryptedDocumentException: Invalid password specified - use 
Biff8EncryptionKey.setCurrentUserPassword() before calling extractor
at 
o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:422)
... 10 more

java.lang.IllegalArgumentException: Start point cannot equalendpoint
at java.awt.LinearGradientPaint.(LinearGradientPaint.java:295)
at 
o.a.p.sl.draw.PathGradientPaint$PathGradientContext.(PathGradientPaint.java:104)
at 
o.a.p.sl.draw.PathGradientPaint.createContext(PathGradientPaint.java:61)
at sun.java2d.pipe.AlphaPaintPipe.startSequence(AlphaPaintPipe.java:84)
at sun.java2d.pipe.AAShapePipe.renderTiles(AAShapePipe.java:168)
at sun.java2d.pipe.AAShapePipe.renderPath(AAShapePipe.java:159)
at sun.java2d.pipe.AAShapePipe.fill(AAShapePipe.java:68)
at 
sun.java2d.pipe.PixelToParallelogramConverter.fill(PixelToParallelogramConverter.java:164)
at sun.java2d.pipe.ValidatePipe.fill(ValidatePipe.java:160)
at sun.java2d.SunGraphics2D.fill(SunGraphics2D.java:2527)
at o.a.p.sl.draw.DrawSimpleShape.draw(DrawSimpleShape.java:89)
at o.a.p.sl.draw.DrawGroupShape.draw(DrawGroupShape.java:60)
at o.a.p.sl.draw.DrawSheet.draw(DrawSheet.java:71)
at o.a.p.sl.draw.DrawSlide.draw(DrawSlide.java:41)
at o.a.p.hslf.usermodel.HSLFSlide.draw(HSLFSlide.java:489)
at o.a.p.stress.SlideShowHandler.renderSlides(SlideShowHandler.java:120)
at 
o.a.p.stress.SlideShowHandler.handleSlideShow(SlideShowHandler.java:43)
at o.a.p.stress.HSLFFileHandler.handleFile(HSLFFileHandler.java:47)

Full information and download links to sample files are at:
report of 3.17-beta1 overall:
http://people.apache.org/~centic/poi_regression/reportsAll/
comparison of 3.16 to 3.17-beta1:
http://people.apache.org/~centic/poi_regression/reports/
comparison of 3.15 to 3.17-beta1:
http://people.apache.org/~centic/poi_regression/reports/index315RC2to317beta1.html

Dominik.

On Wed, Jun 21, 2017 at 10:43 PM, Andreas Beeker <kiwiwi...@apache.org>
wrote:

> I know XML signatures aren't a base functionality of POI, but I'm 
> currently working on #61182 and although the [signature] verification 
> looks good, I can't add signatures which will be successful verified 
> in Libre / Office.
>
> As this is the case with all versions since 3.11 it might be something 
> specific to my machine.
>
> I guess this is not a blocker for the beta - if you think differently, 
> post a veto ...
>
> Andi
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

RE: Is it time for POI 3.17-beta1?

[Allison, Timothy B.]

My run just finished as well.

http://162.242.228.174/reports/reports_poi-3.17-beta1.zip

+1 to roll

I get only one new exception (below) in an xlsx file (there are 7 new zlib/gzip 
in embedded files) and roughly 200 fixed exceptions (mostly wmf) (see: 
exceptions/new_exceptions_in_B_by_mime.xlsx, 
exceptions/fixed_exceptions_in_B_by_mime.xlsx)

There appear to be pretty sizable improvements in the common tokens metric...I 
saw with caveats... ("content/common_token_comparisons_by_mime.xlsx")

I don't see any major red flags in the content diffs 
("content/content_diffs_ignore_exceptions.xlsx")

The one new exception in xlsx:
http://162.242.228.174/docs/commoncrawl2_extras/xlsx/NL/NLBOF7IUZGMNKT3KJSXSQIQYPXOSH3TO
 

ArrayIndexOutOfBounds
at 
org.openxmlformats.schemas.spreadsheetml.x2006.main.impl.CTDxfsImpl.getDxfArray(Unknown
 Source)
at 
org.apache.poi.xssf.usermodel.XSSFTableStyle.(XSSFTableStyle.java
at org.apache.poi.xssf.model.StylesTable.readFrom(StylesTable.java:247)
at org.apache.poi.xssf.model.StylesTable.(StylesTable.java:141)
at 
org.apache.poi.xssf.eventusermodel.XSSFReader.getStylesTable(XSSFReader.java:127)
at 
o.a.t.parser.microsoft.ooxml.XSSFExcelExtractorDecorator.buildXHTML(XSSFExcelExtractorDecorator.java:130)

-Original Message-
From: Dominik Stadler [mailto:dominik.stad...@gmx.at] 
Sent: Friday, June 23, 2017 6:02 AM
To: POI Developers List <dev@poi.apache.org>
Subject: Re: Is it time for POI 3.17-beta1?

Hi,

The 6 errors about password are actually something that I should handle 
differently in the test-framework and is easily fixed there, so only the one 
single failure in drawing slides remains, very nice indeed!

Dominik.

On Fri, Jun 23, 2017 at 11:05 AM, Dominik Stadler <dominik.stad...@gmx.at>
wrote:

> Hi,
>
> Mass testing results are in and look quite good. Out of 1066412 
> documents,
> 136777 are detected as invalid, 76768 cause an error, error rate is 
> 7.2% compared to 7.17% in 3.16 and 7.13% in 3.15, however we do much 
> more checks over time, which hopefully explains the slight increase.
>
> Compared to 3.16 only 7 new errors were seen, 6 of those are related 
> to invalid password being set (probably due to more testing now) and 1 
> related to drawing slides.
>
> o.a.p.EncryptedDocumentException: o.a.p.EncryptedDocumentException: Invalid 
> password specified - use Biff8EncryptionKey.setCurrentUserPassword() before 
> calling extractor
>   at 
> o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:429)
>   at 
> o.a.p.extractor.ExtractorFactory.createExtractor(ExtractorFactory.java:135)
>   at 
> o.a.p.stress.AbstractFileHandler.handleExtractingInternal(AbstractFileHandler.java:88)
>   at 
> o.a.p.stress.AbstractFileHandler.handleExtracting(AbstractFileHandler.
> java:63) Caused by: o.a.p.EncryptedDocumentException: Invalid password 
> specified - use Biff8EncryptionKey.setCurrentUserPassword() before calling 
> extractor
>   at 
> o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:422)
>   ... 10 more
>
> java.lang.IllegalArgumentException: Start point cannot equalendpoint
>   at java.awt.LinearGradientPaint.(LinearGradientPaint.java:295)
>   at 
> o.a.p.sl.draw.PathGradientPaint$PathGradientContext.(PathGradientPaint.java:104)
>   at 
> o.a.p.sl.draw.PathGradientPaint.createContext(PathGradientPaint.java:61)
>   at sun.java2d.pipe.AlphaPaintPipe.startSequence(AlphaPaintPipe.java:84)
>   at sun.java2d.pipe.AAShapePipe.renderTiles(AAShapePipe.java:168)
>   at sun.java2d.pipe.AAShapePipe.renderPath(AAShapePipe.java:159)
>   at sun.java2d.pipe.AAShapePipe.fill(AAShapePipe.java:68)
>   at 
> sun.java2d.pipe.PixelToParallelogramConverter.fill(PixelToParallelogramConverter.java:164)
>   at sun.java2d.pipe.ValidatePipe.fill(ValidatePipe.java:160)
>   at sun.java2d.SunGraphics2D.fill(SunGraphics2D.java:2527)
>   at o.a.p.sl.draw.DrawSimpleShape.draw(DrawSimpleShape.java:89)
>   at o.a.p.sl.draw.DrawGroupShape.draw(DrawGroupShape.java:60)
>   at o.a.p.sl.draw.DrawSheet.draw(DrawSheet.java:71)
>   at o.a.p.sl.draw.DrawSlide.draw(DrawSlide.java:41)
>   at o.a.p.hslf.usermodel.HSLFSlide.draw(HSLFSlide.java:489)
>   at o.a.p.stress.SlideShowHandler.renderSlides(SlideShowHandler.java:120)
>   at 
> o.a.p.stress.SlideShowHandler.handleSlideShow(SlideShowHandler.java:43)
>   at o.a.p.stress.HSLFFileHandler.handleFile(HSLFFileHandler.java:47)
>
> Full information and download links to sample files are at:
> report of 3.17-beta1 overall: http://people.apache.org/~ 
> centic/poi_regression/reportsAll/ comparison of 3.16 to 3.17-beta1: 
> http://people.apache.org/

Re: Is it time for POI 3.17-beta1?

[Dominik Stadler]

Hi,

The 6 errors about password are actually something that I should handle
differently in the test-framework and is easily fixed there, so only the
one single failure in drawing slides remains, very nice indeed!

Dominik.

On Fri, Jun 23, 2017 at 11:05 AM, Dominik Stadler 
wrote:

> Hi,
>
> Mass testing results are in and look quite good. Out of 1066412 documents,
> 136777 are detected as invalid, 76768 cause an error, error rate is 7.2%
> compared to 7.17% in 3.16 and 7.13% in 3.15, however we do much more checks
> over time, which hopefully explains the slight increase.
>
> Compared to 3.16 only 7 new errors were seen, 6 of those are related to
> invalid password being set (probably due to more testing now) and 1
> related to drawing slides.
>
> o.a.p.EncryptedDocumentException: o.a.p.EncryptedDocumentException: Invalid 
> password specified - use Biff8EncryptionKey.setCurrentUserPassword() before 
> calling extractor
>   at 
> o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:429)
>   at 
> o.a.p.extractor.ExtractorFactory.createExtractor(ExtractorFactory.java:135)
>   at 
> o.a.p.stress.AbstractFileHandler.handleExtractingInternal(AbstractFileHandler.java:88)
>   at 
> o.a.p.stress.AbstractFileHandler.handleExtracting(AbstractFileHandler.java:63)
> Caused by: o.a.p.EncryptedDocumentException: Invalid password specified - use 
> Biff8EncryptionKey.setCurrentUserPassword() before calling extractor
>   at 
> o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:422)
>   ... 10 more
>
> java.lang.IllegalArgumentException: Start point cannot equalendpoint
>   at java.awt.LinearGradientPaint.(LinearGradientPaint.java:295)
>   at 
> o.a.p.sl.draw.PathGradientPaint$PathGradientContext.(PathGradientPaint.java:104)
>   at 
> o.a.p.sl.draw.PathGradientPaint.createContext(PathGradientPaint.java:61)
>   at sun.java2d.pipe.AlphaPaintPipe.startSequence(AlphaPaintPipe.java:84)
>   at sun.java2d.pipe.AAShapePipe.renderTiles(AAShapePipe.java:168)
>   at sun.java2d.pipe.AAShapePipe.renderPath(AAShapePipe.java:159)
>   at sun.java2d.pipe.AAShapePipe.fill(AAShapePipe.java:68)
>   at 
> sun.java2d.pipe.PixelToParallelogramConverter.fill(PixelToParallelogramConverter.java:164)
>   at sun.java2d.pipe.ValidatePipe.fill(ValidatePipe.java:160)
>   at sun.java2d.SunGraphics2D.fill(SunGraphics2D.java:2527)
>   at o.a.p.sl.draw.DrawSimpleShape.draw(DrawSimpleShape.java:89)
>   at o.a.p.sl.draw.DrawGroupShape.draw(DrawGroupShape.java:60)
>   at o.a.p.sl.draw.DrawSheet.draw(DrawSheet.java:71)
>   at o.a.p.sl.draw.DrawSlide.draw(DrawSlide.java:41)
>   at o.a.p.hslf.usermodel.HSLFSlide.draw(HSLFSlide.java:489)
>   at o.a.p.stress.SlideShowHandler.renderSlides(SlideShowHandler.java:120)
>   at 
> o.a.p.stress.SlideShowHandler.handleSlideShow(SlideShowHandler.java:43)
>   at o.a.p.stress.HSLFFileHandler.handleFile(HSLFFileHandler.java:47)
>
> Full information and download links to sample files are at:
> report of 3.17-beta1 overall: http://people.apache.org/~
> centic/poi_regression/reportsAll/
> comparison of 3.16 to 3.17-beta1: http://people.apache.org/~
> centic/poi_regression/reports/
> comparison of 3.15 to 3.17-beta1: http://people.apache.org/~
> centic/poi_regression/reports/index315RC2to317beta1.html
>
> Dominik.
>
> On Wed, Jun 21, 2017 at 10:43 PM, Andreas Beeker 
> wrote:
>
>> I know XML signatures aren't a base functionality of POI,
>> but I'm currently working on #61182 and although the [signature]
>> verification
>> looks good, I can't add signatures which will be successful verified in
>> Libre / Office.
>>
>> As this is the case with all versions since 3.11 it might be something
>> specific
>> to my machine.
>>
>> I guess this is not a blocker for the beta - if you think differently,
>> post a veto ...
>>
>> Andi
>>
>>
>

Re: Is it time for POI 3.17-beta1?

[Dominik Stadler]

Hi,

Mass testing results are in and look quite good. Out of 1066412 documents,
136777 are detected as invalid, 76768 cause an error, error rate is 7.2%
compared to 7.17% in 3.16 and 7.13% in 3.15, however we do much more checks
over time, which hopefully explains the slight increase.

Compared to 3.16 only 7 new errors were seen, 6 of those are related to
invalid password being set (probably due to more testing now) and 1 related
to drawing slides.

o.a.p.EncryptedDocumentException: o.a.p.EncryptedDocumentException:
Invalid password specified - use
Biff8EncryptionKey.setCurrentUserPassword() before calling extractor
at 
o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:429)
at 
o.a.p.extractor.ExtractorFactory.createExtractor(ExtractorFactory.java:135)
at 
o.a.p.stress.AbstractFileHandler.handleExtractingInternal(AbstractFileHandler.java:88)
at 
o.a.p.stress.AbstractFileHandler.handleExtracting(AbstractFileHandler.java:63)
Caused by: o.a.p.EncryptedDocumentException: Invalid password
specified - use Biff8EncryptionKey.setCurrentUserPassword() before
calling extractor
at 
o.a.p.extractor.ExtractorFactory.createEncyptedOOXMLExtractor(ExtractorFactory.java:422)
... 10 more

java.lang.IllegalArgumentException: Start point cannot equalendpoint
at java.awt.LinearGradientPaint.(LinearGradientPaint.java:295)
at 
o.a.p.sl.draw.PathGradientPaint$PathGradientContext.(PathGradientPaint.java:104)
at 
o.a.p.sl.draw.PathGradientPaint.createContext(PathGradientPaint.java:61)
at sun.java2d.pipe.AlphaPaintPipe.startSequence(AlphaPaintPipe.java:84)
at sun.java2d.pipe.AAShapePipe.renderTiles(AAShapePipe.java:168)
at sun.java2d.pipe.AAShapePipe.renderPath(AAShapePipe.java:159)
at sun.java2d.pipe.AAShapePipe.fill(AAShapePipe.java:68)
at 
sun.java2d.pipe.PixelToParallelogramConverter.fill(PixelToParallelogramConverter.java:164)
at sun.java2d.pipe.ValidatePipe.fill(ValidatePipe.java:160)
at sun.java2d.SunGraphics2D.fill(SunGraphics2D.java:2527)
at o.a.p.sl.draw.DrawSimpleShape.draw(DrawSimpleShape.java:89)
at o.a.p.sl.draw.DrawGroupShape.draw(DrawGroupShape.java:60)
at o.a.p.sl.draw.DrawSheet.draw(DrawSheet.java:71)
at o.a.p.sl.draw.DrawSlide.draw(DrawSlide.java:41)
at o.a.p.hslf.usermodel.HSLFSlide.draw(HSLFSlide.java:489)
at o.a.p.stress.SlideShowHandler.renderSlides(SlideShowHandler.java:120)
at 
o.a.p.stress.SlideShowHandler.handleSlideShow(SlideShowHandler.java:43)
at o.a.p.stress.HSLFFileHandler.handleFile(HSLFFileHandler.java:47)

Full information and download links to sample files are at:
report of 3.17-beta1 overall:
http://people.apache.org/~centic/poi_regression/reportsAll/
comparison of 3.16 to 3.17-beta1:
http://people.apache.org/~centic/poi_regression/reports/
comparison of 3.15 to 3.17-beta1:
http://people.apache.org/~centic/poi_regression/reports/index315RC2to317beta1.html

Dominik.

On Wed, Jun 21, 2017 at 10:43 PM, Andreas Beeker 
wrote:

> I know XML signatures aren't a base functionality of POI,
> but I'm currently working on #61182 and although the [signature]
> verification
> looks good, I can't add signatures which will be successful verified in
> Libre / Office.
>
> As this is the case with all versions since 3.11 it might be something
> specific
> to my machine.
>
> I guess this is not a blocker for the beta - if you think differently,
> post a veto ...
>
> Andi
>
>

Re: Is it time for POI 3.17-beta1?

[Andreas Beeker]

I know XML signatures aren't a base functionality of POI,
but I'm currently working on #61182 and although the [signature] verification
looks good, I can't add signatures which will be successful verified in Libre / 
Office.

As this is the case with all versions since 3.11 it might be something specific
to my machine.

I guess this is not a blocker for the beta - if you think differently, post a 
veto ...

Andi



signature.asc
Description: OpenPGP digital signature

Re: Is it time for POI 3.17-beta1?

[Greg Woolsey]

+1 from me.  Nothing pending atm, table/workbook style/theme changes in and
tested.

On Tue, Jun 20, 2017 at 12:23 PM Allison, Timothy B. <talli...@mitre.org>
wrote:

> +1 -- my few small changes are in.  I'll kick off my regression tests
> tonight or tomorrow.
>
> -Original Message-
> From: Dominik Stadler [mailto:dominik.stad...@gmx.at]
> Sent: Tuesday, June 20, 2017 10:00 AM
> To: POI Developers List <dev@poi.apache.org>
> Subject: Re: Is it time for POI 3.17-beta1?
>
> Ok with me, I will try to kick off a test-run later today, typically runs
> for > 24h...
>
> Dominik.
>
> On Mon, Jun 19, 2017 at 7:20 PM, Javen O'Neal <one...@apache.org> wrote:
>
> > +1 from me.
> >
> > On Jun 19, 2017 04:26, "Allison, Timothy B." <talli...@mitre.org> wrote:
> >
> > > +1
> > >
> > > I'd like to get in some small modifications I've been meaning to work
> on.
> > > I'll have time today.
> > >
> > > -Original Message-
> > > From: Andreas Beeker [mailto:kiwiwi...@apache.org]
> > > Sent: Monday, June 19, 2017 4:09 AM
> > > To: POI Developers List <dev@poi.apache.org>
> > > Subject: Is it time for POI 3.17-beta1?
> > >
> > > Hi *,
> > >
> > > there are quite some changes since the last final in the changelog -
> > > how about pushing out the next beta?
> > >
> > > I would be available as release manager ...
> > >
> > > As I made substantial changes to HPSF - I'm curious about the
> > common-crawl
> > > & Co. tests, i.e. the integration test have been modified to test
> > > HPSF
> > now,
> > > so I'm sure there will be new errors reported in this area ...
> > >
> > > Andi
> > >
> > >
> > >
> > > 
> > > - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For
> > > additional commands, e-mail: dev-h...@poi.apache.org
> > >
> > >
> >
>

RE: Is it time for POI 3.17-beta1?

[Allison, Timothy B.]

+1 -- my few small changes are in.  I'll kick off my regression tests tonight 
or tomorrow.

-Original Message-
From: Dominik Stadler [mailto:dominik.stad...@gmx.at] 
Sent: Tuesday, June 20, 2017 10:00 AM
To: POI Developers List <dev@poi.apache.org>
Subject: Re: Is it time for POI 3.17-beta1?

Ok with me, I will try to kick off a test-run later today, typically runs for > 
24h...

Dominik.

On Mon, Jun 19, 2017 at 7:20 PM, Javen O'Neal <one...@apache.org> wrote:

> +1 from me.
>
> On Jun 19, 2017 04:26, "Allison, Timothy B." <talli...@mitre.org> wrote:
>
> > +1
> >
> > I'd like to get in some small modifications I've been meaning to work on.
> > I'll have time today.
> >
> > -Original Message-
> > From: Andreas Beeker [mailto:kiwiwi...@apache.org]
> > Sent: Monday, June 19, 2017 4:09 AM
> > To: POI Developers List <dev@poi.apache.org>
> > Subject: Is it time for POI 3.17-beta1?
> >
> > Hi *,
> >
> > there are quite some changes since the last final in the changelog - 
> > how about pushing out the next beta?
> >
> > I would be available as release manager ...
> >
> > As I made substantial changes to HPSF - I'm curious about the
> common-crawl
> > & Co. tests, i.e. the integration test have been modified to test 
> > HPSF
> now,
> > so I'm sure there will be new errors reported in this area ...
> >
> > Andi
> >
> >
> >
> > 
> > - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For 
> > additional commands, e-mail: dev-h...@poi.apache.org
> >
> >
>

Re: Is it time for POI 3.17-beta1?

[Dominik Stadler]

Ok with me, I will try to kick off a test-run later today, typically runs
for > 24h...

Dominik.

On Mon, Jun 19, 2017 at 7:20 PM, Javen O'Neal  wrote:

> +1 from me.
>
> On Jun 19, 2017 04:26, "Allison, Timothy B."  wrote:
>
> > +1
> >
> > I'd like to get in some small modifications I've been meaning to work on.
> > I'll have time today.
> >
> > -Original Message-
> > From: Andreas Beeker [mailto:kiwiwi...@apache.org]
> > Sent: Monday, June 19, 2017 4:09 AM
> > To: POI Developers List 
> > Subject: Is it time for POI 3.17-beta1?
> >
> > Hi *,
> >
> > there are quite some changes since the last final in the changelog - how
> > about pushing out the next beta?
> >
> > I would be available as release manager ...
> >
> > As I made substantial changes to HPSF - I'm curious about the
> common-crawl
> > & Co. tests, i.e. the integration test have been modified to test HPSF
> now,
> > so I'm sure there will be new errors reported in this area ...
> >
> > Andi
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> > For additional commands, e-mail: dev-h...@poi.apache.org
> >
> >
>

RE: Is it time for POI 3.17-beta1?

[Javen O'Neal]

+1 from me.

On Jun 19, 2017 04:26, "Allison, Timothy B."  wrote:

> +1
>
> I'd like to get in some small modifications I've been meaning to work on.
> I'll have time today.
>
> -Original Message-
> From: Andreas Beeker [mailto:kiwiwi...@apache.org]
> Sent: Monday, June 19, 2017 4:09 AM
> To: POI Developers List 
> Subject: Is it time for POI 3.17-beta1?
>
> Hi *,
>
> there are quite some changes since the last final in the changelog - how
> about pushing out the next beta?
>
> I would be available as release manager ...
>
> As I made substantial changes to HPSF - I'm curious about the common-crawl
> & Co. tests, i.e. the integration test have been modified to test HPSF now,
> so I'm sure there will be new errors reported in this area ...
>
> Andi
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

RE: Is it time for POI 3.17-beta1?

[Allison, Timothy B.]

+1

I'd like to get in some small modifications I've been meaning to work on.  I'll 
have time today.

-Original Message-
From: Andreas Beeker [mailto:kiwiwi...@apache.org] 
Sent: Monday, June 19, 2017 4:09 AM
To: POI Developers List 
Subject: Is it time for POI 3.17-beta1?

Hi *,

there are quite some changes since the last final in the changelog - how about 
pushing out the next beta?

I would be available as release manager ...

As I made substantial changes to HPSF - I'm curious about the common-crawl & 
Co. tests, i.e. the integration test have been modified to test HPSF now, so 
I'm sure there will be new errors reported in this area ...

Andi



-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org