[jira] [Comment Edited] (TIKA-3263) WriteLimitReachedException is not public

2021-04-15 Thread Tim Allison (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322487#comment-17322487 ] Tim Allison edited comment on TIKA-3263 at 4/15/21, 9:25 PM: -

[jira] [Commented] (TIKA-3263) WriteLimitReachedException is not public

2021-04-15 Thread Tim Allison (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322487#comment-17322487 ] Tim Allison commented on TIKA-3263: --- [~kkrugler], I wasn't around when this was implemen

[jira] [Comment Edited] (TIKA-3263) WriteLimitReachedException is not public

2021-04-15 Thread Aaron Weber (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322479#comment-17322479 ] Aaron Weber edited comment on TIKA-3263 at 4/15/21, 8:55 PM: -

[jira] [Commented] (TIKA-3263) WriteLimitReachedException is not public

2021-04-15 Thread Aaron Weber (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322479#comment-17322479 ] Aaron Weber commented on TIKA-3263: --- Just ran into this as well.  Being able to catch th

[jira] [Commented] (TIKA-3357) Remove ambiguity in request handlers

2021-04-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322398#comment-17322398 ] ASF GitHub Bot commented on TIKA-3357: -- Subhajitdas298 opened a new pull request #427

[GitHub] [tika] Subhajitdas298 opened a new pull request #427: [TIKA-3357] removes ambiguity by choosing handler based on produce type

2021-04-15 Thread GitBox
Subhajitdas298 opened a new pull request #427: URL: https://github.com/apache/tika/pull/427 Added Resource comparator based to produce type. In an ambiguous call, request handler will be chosen based on the type of data it returns. **Current priority is set as:** MediaType.TEXT

[jira] [Created] (TIKA-3357) Remove ambiguity in request handlers

2021-04-15 Thread Subhajit Das (Jira)
Subhajit Das created TIKA-3357: -- Summary: Remove ambiguity in request handlers Key: TIKA-3357 URL: https://issues.apache.org/jira/browse/TIKA-3357 Project: Tika Issue Type: Improvement

RE: Test failure

2021-04-15 Thread Peter Kronenberg
It wasn't a totally clean pull, but I didn't have anything else there. I had stuff in other branches, but when it failed, I tried it on a clean main. Here's the command line I used: mvn clean install -pl :tika-parsers-classic-package -am Since my pull request was processed with no probl

[jira] [Commented] (TIKA-3355) Integrate fakeload into MockParser

2021-04-15 Thread Hudson (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322319#comment-17322319 ] Hudson commented on TIKA-3355: -- SUCCESS: Integrated in Jenkins build Tika » tika-branch1x-jdk

[jira] [Commented] (TIKA-3355) Integrate fakeload into MockParser

2021-04-15 Thread Hudson (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322318#comment-17322318 ] Hudson commented on TIKA-3355: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #1

Re: Test failure

2021-04-15 Thread Tim Allison
HI found a couple of other things that I fixed on Windows just now, but I'm not able to replicate it. Are you getting that failure with a clean pull/clone? On Thu, Apr 15, 2021 at 11:48 AM Tim Allison wrote: > Thank you for sharing! > > Not able to replicate on linux...trying my Windows

[GitHub] [tika] tballison merged pull request #426: Fix up exception handling for invalid config

2021-04-15 Thread GitBox
tballison merged pull request #426: URL: https://github.com/apache/tika/pull/426 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please co

[jira] [Resolved] (TIKA-3356) Broken xhtml with extractImages in 2.x

2021-04-15 Thread Tim Allison (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-3356. --- Resolution: Not A Problem the unit test is concatenating recursive metadata content...that is an ill

[jira] [Created] (TIKA-3356) Broken xhtml with extractImages in 2.x

2021-04-15 Thread Tim Allison (Jira)
Tim Allison created TIKA-3356: - Summary: Broken xhtml with extractImages in 2.x Key: TIKA-3356 URL: https://issues.apache.org/jira/browse/TIKA-3356 Project: Tika Issue Type: Task Repo

Re: Test failure

2021-04-15 Thread Tim Allison
Thank you for sharing! Not able to replicate on linux...trying my Windows laptop. Unrelated...there's something really broken with the xhtml in that there are two bodies. I can replicate this on linux. Will open an issue... On Thu, Apr 15, 2021 at 10:04 AM Peter Kronenberg wrote: > We’re get

[GitHub] [tika] peterkronenberg commented on pull request #426: Fix up exception handling for invalid config

2021-04-15 Thread GitBox
peterkronenberg commented on pull request #426: URL: https://github.com/apache/tika/pull/426#issuecomment-820450345 Was doing some error recovery testing on the config files for my own application, and discovered that the exception handling for an invalid config value had too many layers i

[GitHub] [tika] peterkronenberg opened a new pull request #426: Fix up exception handling for invalid config

2021-04-15 Thread GitBox
peterkronenberg opened a new pull request #426: URL: https://github.com/apache/tika/pull/426 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika

Test failure

2021-04-15 Thread Peter Kronenberg
We're getting a test failure. I don't see any recent check-ins that would be causing this, so maybe it's been there for awhile (I don't always run the tests) [INFO] Results: [INFO] [ERROR] Failures: [ERROR] TesseractOCRParserTest.testOCROutputsHOCR:105->TikaTest.assertContains:79 http://www.w

[jira] [Comment Edited] (TIKA-3354) [tika-parsers] Wrong commons-io version imported

2021-04-15 Thread Arnaud MERGEY (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321960#comment-17321960 ] Arnaud MERGEY edited comment on TIKA-3354 at 4/15/21, 7:18 AM: -

[jira] [Commented] (TIKA-3354) [tika-parsers] Wrong commons-io version imported

2021-04-15 Thread Arnaud MERGEY (Jira)
[ https://issues.apache.org/jira/browse/TIKA-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321960#comment-17321960 ] Arnaud MERGEY commented on TIKA-3354: - digging more about this I think I found the exp