[Bug 64027] This is regarding the below method - IOUtils.setByteArrayMaxOverride

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=64027

--- Comment #2 from Sushmita Nag  ---
hi,

So, is there any solution for the above issue ? As our Customer is totally
blocked because of the above issue where in they are not able to upload a
certain document of 2.5 MB because of
org.apache.poi.util.RecordFormatException.

Could you please let us know how do we proceed from here ?

Regards,
Sushmita

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Re: Need help getting Specs for One Note versions older than 2012

[Nick Burch]

On Mon, 23 Dec 2019, Nicholas DiPiazza wrote:
Unfortunately, the formats are *drastically* different. Any attempt to 
reverse engineer would be a massive project... mostly impossible.


Pesky. I have heard of that with products that get bought-in then redone, 
unusual for Microsoft fully in-house



I can use a java program based on the linux "strings" program which will
make two passes through the older OneNote files.

Does tika or POI already come equipped with a utility that can detect 
the likelihood of useful text versus garbage?


Tika has some stuff for that, part of Tika-eval. Tim Allison is the expert 
on that bit of the code


I'd suggest you try with that, then see if you can identify some common 
header/block patterns for the bits before the real text


Nick

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

Re: Need help getting Specs for One Note versions older than 2012

[Nicholas DiPiazza]

Thanks for the response Nick.

Unfortunately, the formats are *drastically* different. Any attempt to
reverse engineer would be a massive project... mostly impossible.

I can use a java program based on the linux "strings" program which will
make two passes through the older OneNote files.

pass # 1) extract ascii text
pass # 2) extract utf-16LE text.

Does tika or POI already come equipped with a utility that can detect the
likelihood of useful text versus garbage?

For example:

*p(*K~6a]tNKkZB"_aa+XzeyNs~?*

versus

*Some useful text within the OneNote document*

It would be good to get SOME sort of indexable output from OneNote <= 2010
documents instead of nothing.

Re: Next version 4.2?

[kiwiwings]

I saw a lot of @removal(4.2) and hence I've asked.
I would now update those to @removal(5.0).

My problem with cleaning up our technical debt is,
that this often affects also the API and needs to be
done on the major version change. In the other hand
we like to have a stable API for a longer period.

I guess the key to solve this, is a better branching method.
So we can clean up while the minor versions are updated/back ported.

As I'm only a very casual GIT user, I would need some lessons on how to do
it effectively. With SVN feature branches and a parallel development this
will be more effort, which I like to avoid.

If GIT is the answer to such problems,
we could vote about it and eventually check with INFRA to switch the repo.

Andi.



--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html

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

Re: Need help getting Specs for One Note versions older than 2012

[Nick Burch]

On Mon, 23 Dec 2019, Nicholas DiPiazza wrote:
I'm needing some help gathering the older Spec documentation for 
Microsoft OneNote prior to year 2012. See 
https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-onestore/ae670cd2-4b38-4b24-82d1-87cfb2cc3725 
and you'll notice that the specifications are available beginning 1.5 
which was released in 2012.


Unfortunately, you probably can't, at least not very quickly.

Microsoft do have internal docs on many (but not all) file formats coverin 
much (but not all) of the details. I believe that the public docs are 
largely written from scratch. Assuming nothing has changed in the last few 
years, the doc writers read the internal stuff, go spend quite a bit of 
time chatting with the devs, read bits of the code, then write.


You can certainly ask Microsoft if they'd mind releasing the earlier ones, 
and they'll add it to the wish-list. Unless there's minimal changes from 
the published stuff, as old formats are a bit niche, you may well be 
waiting rather a long time for them to get round to it. (Most of the focus 
is on the new stuff)



That said, the file formats from Microsoft tend to evolve, so it'll 
probably be similar to what you already have. Possibly the header block 
will be smaller (fewer flags / shorter lengths), possibly missing some 
other parts, maybe with some bits joined or split out, but likely similar. 
Good luck!


Nick

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

Need help getting Specs for One Note versions older than 2012

[Nicholas DiPiazza]

Dear Apache folks,

I'm needing some help gathering the older Spec documentation for Microsoft
OneNote prior to year 2012. See
https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-onestore/ae670cd2-4b38-4b24-82d1-87cfb2cc3725
and you'll notice that the specifications are available beginning 1.5 which
was released in 2012.

How can I get the older specifications?

-Nicholas

Re: Next version 4.2?

[PJ Fanning]

 I agree with Mark that we should wait for 5.0.0 to remove more deprecated 
methods.
Our previous policy was to wait 2 releases (eg 3.15 to 3.17) - can we agree 
that major releases like 5.0.0, 6.0.0 is when we will remove deprecated 
methods, in future? 

On Monday 23 December 2019, 14:39:46 GMT+1, Mark Murphy 
 wrote:  
 
 This makes things a lot easier for folks using Maven for dependencies. What
is the harm in letting things stay there until 5.0?

On Mon, Dec 23, 2019 at 8:37 AM Mark Murphy  wrote:

> With Semantic versioning, you can't remove deprecates until a major
> version change.
>
> On Sun, Dec 22, 2019 at 3:46 PM Andreas Beeker 
> wrote:
>
>> Hi,
>>
>> I'd like to remove the deprecates for 4.2.
>>
>> What will be our next version?
>>
>> Andi
>>
>>
>>
  

Re[2]: Next version 4.2?

[Абжанов Д . Ж .]

Please fix the error related to the shiftRows method in POI 4.1.1

shiftRows don’t work



Отправлено из мобильной Почты Mail.ru


понедельник, 23 декабря 2019 г., 19:38 +0600 от jmarkmur...@gmail.com  
:
>With Semantic versioning, you can't remove deprecates until a major version
>change.
>
>On Sun, Dec 22, 2019 at 3:46 PM Andreas Beeker < kiwiwi...@apache.org > wrote:
>
>> Hi,
>>
>> I'd like to remove the deprecates for 4.2.
>>
>> What will be our next version?
>>
>> Andi
>>
>>
>>
>

Re: Next version 4.2?

[Mark Murphy]

This makes things a lot easier for folks using Maven for dependencies. What
is the harm in letting things stay there until 5.0?

On Mon, Dec 23, 2019 at 8:37 AM Mark Murphy  wrote:

> With Semantic versioning, you can't remove deprecates until a major
> version change.
>
> On Sun, Dec 22, 2019 at 3:46 PM Andreas Beeker 
> wrote:
>
>> Hi,
>>
>> I'd like to remove the deprecates for 4.2.
>>
>> What will be our next version?
>>
>> Andi
>>
>>
>>

Re: Next version 4.2?

[Mark Murphy]

With Semantic versioning, you can't remove deprecates until a major version
change.

On Sun, Dec 22, 2019 at 3:46 PM Andreas Beeker  wrote:

> Hi,
>
> I'd like to remove the deprecates for 4.2.
>
> What will be our next version?
>
> Andi
>
>
>

Build failed in Jenkins: POI-DSL-Maven #984

[Apache Jenkins Server]

See 


Changes:

[fanningpj] convert some tabs to spaces


--
[...truncated 132.20 KB...]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
org.apache.poi.ss.formula.functions.TestIPMT
Running org.apache.poi.ss.formula.functions.TestDGetFunctionsFromSpreadsheet
Tests run: 80, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec - in 
org.apache.poi.ss.formula.functions.TestDGetFunctionsFromSpreadsheet
Running org.apache.poi.ss.formula.functions.TestRowCol
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.formula.functions.TestRowCol
Running org.apache.poi.ss.formula.functions.TestComplexFunctionsFromSpreadsheet
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.formula.functions.TestComplexFunctionsFromSpreadsheet
Running org.apache.poi.ss.formula.functions.TestTrendFunctionsFromSpreadsheet
Tests run: 41, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.042 sec - in 
org.apache.poi.ss.formula.functions.TestTrendFunctionsFromSpreadsheet
Running org.apache.poi.ss.formula.functions.TestGeomean
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.21 sec - in 
org.apache.poi.ss.formula.functions.TestGeomean
Running org.apache.poi.ss.formula.functions.TestMatch
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
org.apache.poi.ss.formula.functions.TestMatch
Running org.apache.poi.ss.formula.functions.TestDec2Bin
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec - in 
org.apache.poi.ss.formula.functions.TestDec2Bin
Running org.apache.poi.ss.formula.TestCellCacheEntry
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.formula.TestCellCacheEntry
Running org.apache.poi.ss.formula.TestFunctionRegistry
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.formula.TestFunctionRegistry
Running org.apache.poi.ss.TestSpreadsheetVersion
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.TestSpreadsheetVersion
Running org.apache.poi.ss.util.TestCellRangeUtil
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.util.TestCellRangeUtil
Running org.apache.poi.ss.util.TestCellAddress
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.util.TestCellAddress
Running org.apache.poi.ss.util.TestSheetUtil
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in 
org.apache.poi.ss.util.TestSheetUtil
Running org.apache.poi.ss.util.TestDateFormatConverter
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.738 sec - in 
org.apache.poi.ss.util.TestDateFormatConverter
Running org.apache.poi.ss.util.TestPropertyTemplate
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.051 sec - in 
org.apache.poi.ss.util.TestPropertyTemplate
Running org.apache.poi.ss.util.TestSheetBuilder
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in 
org.apache.poi.ss.util.TestSheetBuilder
Running org.apache.poi.ss.util.TestNumberComparer
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.052 sec - in 
org.apache.poi.ss.util.TestNumberComparer
Running org.apache.poi.ss.util.TestAreaReference
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.util.TestAreaReference
Running org.apache.poi.ss.util.TestNumberToTextConverter
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in 
org.apache.poi.ss.util.TestNumberToTextConverter
Running org.apache.poi.ss.util.TestWorkbookUtil
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.util.TestWorkbookUtil
Running org.apache.poi.ss.util.TestHSSFCellUtil
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec - in 
org.apache.poi.ss.util.TestHSSFCellUtil
Running org.apache.poi.ss.util.TestExpandedDouble
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.util.TestExpandedDouble
Running org.apache.poi.ss.util.TestCellReference
Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.418 sec - in 
org.apache.poi.ss.util.TestCellReference
Running org.apache.poi.ss.util.TestCellRangeAddress
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.poi.ss.util.TestCellRangeAddress
Running org.apache.poi.ss.util.cellwalk.TestCellWalk
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
org.apache.poi.ss.util.cellwalk.TestCellWalk
Running org.apache.poi.ss.util.TestRegionUtil
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec - in 
org.apache.poi.ss.util.TestRegionUtil
Running 

[Bug 64027] This is regarding the below method - IOUtils.setByteArrayMaxOverride

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=64027

PJ Fanning  changed:

   What|Removed |Added

 OS||All

--- Comment #1 from PJ Fanning  ---
There are problems with the max override code - see
https://bz.apache.org/bugzilla/show_bug.cgi?id=64001

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org