[Bug 68094] In 5.2.4 After called autoSizeColumn function, the returned column width is smaller than in 5.2.3, which makes the columns to be cut off

2025-09-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68094 --- Comment #21 from PJ Fanning --- There are still some unreleased changes so the most practical solution for people who think autoSizeColumn is making the columns too narrow or too wide is to make the autosize calls and then to loop over the

[Bug 69794] Unable to print excel report

2025-08-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69794 --- Comment #1 from PJ Fanning --- We don't accept advertising spam. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail

[Bug 69794] Unable to print excel report

2025-08-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69794 PJ Fanning changed: What|Removed |Added OS||All Resolution

[Bug 69794] New: Unable to print excel report

2025-08-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69794 Bug ID: 69794 Summary: Unable to print excel report Product: POI Version: unspecified Hardware: PC Status: NEW Severity: normal Priority: P2

[Bug 69742] An error occurred when converting a word file to XWPFDocument, indicating java.io.IOException: Failed to read zip entry source.

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69742 Dominik Stadler changed: What|Removed |Added Resolution|--- |INVALID Status|NEEDINFO

[Bug 69628] unable to reduce memory usage when parsing docx file

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69628 PJ Fanning changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 69656] Inconsistency in Paragraph Layouting when rendering PNG/SVG out of POI.

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69656 Dominik Stadler changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this

[Bug 69637] Prevent users from assigning tables an invalid name

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69637 Dominik Stadler changed: What|Removed |Added Severity|normal |enhancement -- You are receiving

[Bug 69628] unable to reduce memory usage when parsing docx file

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69628 Dominik Stadler changed: What|Removed |Added Keywords||PatchAvailable -- You are

[Bug 69609] The .doc file with the table is corrupted.

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69609 Dominik Stadler changed: What|Removed |Added OS||All -- You are receiving this mail

[Bug 69563] Creating a large Excel file leads to: ArithmeticException: integer overflow

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69563 Dominik Stadler changed: What|Removed |Added Status|NEW |RESOLVED Resolution

[Bug 69547] hope return value of getText on paragraph include numbering symbols

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69547 Dominik Stadler changed: What|Removed |Added Severity|normal |enhancement -- You are receiving

[Bug 69544] Unable to process XLSX charts exported from Google Sheets

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69544 Dominik Stadler changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this

[Bug 69541] Unable to read the file properly due to some formatting in this doc file

2025-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69541 Dominik Stadler changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEEDINFO

[Bug 69791] New: MINIFS fails to evaluate in Excel

2025-08-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69791 Bug ID: 69791 Summary: MINIFS fails to evaluate in Excel Product: POI Version: 5.4.2-FINAL Hardware: PC OS: Mac OS X 10.1 Status: NEW Severity: normal

[Bug 68094] In 5.2.4 After called autoSizeColumn function, the returned column width is smaller than in 5.2.3, which makes the columns to be cut off

2025-08-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68094 Daniel changed: What|Removed |Added CC||daniel77lun...@icloud.com -- You are

[Bug 60102] Improve error message when writing a document that has been closed

2025-08-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60102 Daniel changed: What|Removed |Added Alias||Carro, trygg -- You are receiving this mail

[Bug 69784] New: Double borders and borders over hanging PPTX2PNG

2025-08-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69784 Bug ID: 69784 Summary: Double borders and borders over hanging PPTX2PNG Product: POI Version: 5.4.2-FINAL Hardware: PC Status: NEW Severity: normal Priority

[Bug 69777] When using XSSF, calling cell.setCellType(CellType.STRING) on a cell with original type STCellType.INLINE_STR results in the cell value becoming empty.

2025-08-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69777 Matafagafo changed: What|Removed |Added CC||matafag...@gmail.com -- You are

[Bug 69777] When using XSSF, calling cell.setCellType(CellType.STRING) on a cell with original type STCellType.INLINE_STR results in the cell value becoming empty.

2025-08-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69777 --- Comment #1 from PJ Fanning --- There is nowhere (to my knowledge) that we have documented that setCellType preserves the value. You should never assume what the behaviour is, especially when it is ambiguous. If we change this, we are

[Bug 69777] New: When using XSSF, calling cell.setCellType(CellType.STRING) on a cell with original type STCellType.INLINE_STR results in the cell value becoming empty.

2025-08-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69777 Bug ID: 69777 Summary: When using XSSF, calling cell.setCellType(CellType.STRING) on a cell with original type STCellType.INLINE_STR results in the cell value

[Bug 69769] XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace

2025-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69769 Tim Heger changed: What|Removed |Added CC||johannes.summerer@krause-sc

[Bug 69769] XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace

2025-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69769 Tim Heger changed: What|Removed |Added CC||tim.he...@krause-schopp.de -- You are

[Bug 69769] XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace

2025-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69769 --- Comment #5 from Tim Heger --- (In reply to PJ Fanning from comment #1) > What is the origin of the broken xlsx - that is what application or library > produced it? We are a leading company in the field of data standardizati

[Bug 69769] XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace

2025-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69769 --- Comment #4 from PJ Fanning --- Surely you know which customer sent you the broken file. Is there PII in the file because that will get us in trouble? If there is no PII in the file, can't you ask the customer to find out what applic

[Bug 69769] XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace

2025-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69769 --- Comment #3 from PJ Fanning --- Not a bug. You said so yourself - read the ECMA-376 spec. I looked the poi-ooxml code and trimming strings before parsing them as numbers is rare in the code. -- You are receiving this mail because: You

[Bug 69769] XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace

2025-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69769 --- Comment #2 from Tim Heger --- (In reply to PJ Fanning from comment #1) > What is the origin of the broken xlsx - that is what application or library > produced it? We are a leading company in the field of data standardizati

[Bug 69769] XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace

2025-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69769 --- Comment #1 from PJ Fanning --- What is the origin of the broken xlsx - that is what application or library produced it? -- You are receiving this mail because: You are the assignee for the bug

[Bug 69769] New: XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace

2025-08-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69769 Bug ID: 69769 Summary: XSSFSheetXMLHandler throws NumberFormatException when in t="s" cell contains trailing whitespace Product: POI Version: 5.4.1-FINAL Ha

[Bug 69749] XSSFHyperlink error setting address

2025-07-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69749 --- Comment #3 from szfz...@gmail.com --- (In reply to sfisque from comment #1) > not a bug. it's telling you exactly where the issue is, in the stacktrace. > > '{' is not a valid URI character. try uri-encoding

[Bug 69749] XSSFHyperlink error setting address

2025-07-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69749 --- Comment #2 from szfz...@gmail.com --- Why uri-encode? Both Microsoft Office Excel and Chrome accept '{' in url already. -- You are receiving this mail because: You are the assignee f

[Bug 69749] XSSFHyperlink error setting address

2025-07-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69749 sfis...@gmail.com changed: What|Removed |Added OS||All --- Comment #1 from sfis

[Bug 69749] New: XSSFHyperlink error setting address

2025-07-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69749 Bug ID: 69749 Summary: XSSFHyperlink error setting address Product: POI Version: 5.4.1-FINAL Hardware: PC Status: NEW Severity: minor Priority: P2

[Bug 69744] XWPFTable.getTableAlignment throws IllegalArgumentException

2025-07-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69744 PJ Fanning changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 69744] XWPFTable.getTableAlignment throws IllegalArgumentException

2025-07-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69744 --- Comment #3 from Jacobo Aragunde Pérez --- (In reply to PJ Fanning from comment #2) > This looks like a bug to me. I'm happier breaking stuff when there is bona > fide bug. Can you create a PR that adds the 5 correct enu

[Bug 69744] XWPFTable.getTableAlignment throws IllegalArgumentException

2025-07-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69744 --- Comment #2 from PJ Fanning --- This looks like a bug to me. I'm happier breaking stuff when there is bona fide bug. Can you create a PR that adds the 5 correct enum values in TableRowAlign? -- You are receiving this mail because: Yo

[Bug 69744] XWPFTable.getTableAlignment throws IllegalArgumentException

2025-07-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69744 --- Comment #1 from Jacobo Aragunde Pérez --- I started taking a look at this, the trivial approach would be to add TableRowAlign.START and END so we would map the possible jc values like this: public enum TableRowAlign { LEFT

[Bug 69744] New: XWPFTable.getTableAlignment throws IllegalArgumentException

2025-07-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69744 Bug ID: 69744 Summary: XWPFTable.getTableAlignment throws IllegalArgumentException Product: POI Version: 5.4.x-dev Hardware: PC OS: Linux

[Bug 69742] An error occurred when converting a word file to XWPFDocument, indicating java.io.IOException: Failed to read zip entry source.

2025-07-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69742 PJ Fanning changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #3 from PJ Fanning

[Bug 69705] ZIP BOMB DETECTED WHILE WORKING WITH apache poi 5.0.0

2025-07-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69705 --- Comment #9 from Dominik Stadler --- Sounds like a different problem, please share details including error messages and how you use Apache POI in a new issue. Ideally with a self-sufficient code-sample which allows to reproduce the problem

[Bug 69742] An error occurred when converting a word file to XWPFDocument, indicating java.io.IOException: Failed to read zip entry source.

2025-07-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69742 --- Comment #2 from aniu007 <969675...@qq.com> --- Related code try{ File wordFile = new File("D:\\website\\temp\\myWordFile.docx"); File htmlFile = new File("D:\\website\\temp\\myWordFile.html"); Strin

[Bug 69742] An error occurred when converting a word file to XWPFDocument, indicating java.io.IOException: Failed to read zip entry source.

2025-07-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69742 aniu007 <969675...@qq.com> changed: What|Removed |Added OS||All --- Comment #

[Bug 69742] New: An error occurred when converting a word file to XWPFDocument, indicating java.io.IOException: Failed to read zip entry source.

2025-07-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69742 Bug ID: 69742 Summary: An error occurred when converting a word file to XWPFDocument, indicating java.io.IOException: Failed to read zip entry source. Product: POI

[Bug 69705] ZIP BOMB DETECTED WHILE WORKING WITH apache poi 5.0.0

2025-07-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69705 --- Comment #8 from Rakhi Barayanan --- Hi Dominik, Issue is still the same.We are not able to generate the complete report.If the number of rows are less its creating good.But as the row number increases it is throwing error.Earlier the

[Bug 69705] ZIP BOMB DETECTED WHILE WORKING WITH apache poi 5.0.0

2025-07-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69705 Dominik Stadler changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

[Bug 69720] Paragraph alignment value defaults to left, null not allowed

2025-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69720 PJ Fanning changed: What|Removed |Added Status|NEW |RESOLVED Resolution

[Bug 69705] ZIP BOMB DETECTED WHILE WORKING WITH apache poi 5.0.0

2025-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69705 Rakhi Barayanan changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution

[Bug 69720] Paragraph alignment value defaults to left, null not allowed

2025-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69720 --- Comment #2 from Jacobo Aragunde Pérez --- Created attachment 40055 --> https://bz.apache.org/bugzilla/attachment.cgi?id=40055&action=edit Test case, saved by Word Test case where both calls to getAlignment() return LEFT. --

[Bug 69727] XSSFSheet Wrong count when call removeMergedRegion and addMergedRegion

2025-07-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69727 PJ Fanning changed: What|Removed |Added Status|NEW |RESOLVED Resolution

[Bug 69718] xval if not specified is giving error instead of taking a default value

2025-07-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69718 PJ Fanning changed: What|Removed |Added Severity|critical|normal OS|Mac OS X 10.1

[Bug 69727] XSSFSheet Wrong count when call removeMergedRegion and addMergedRegion

2025-07-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69727 --- Comment #1 from PJ Fanning --- I've created a PR - https://github.com/apache/poi/pull/837 -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 69720] Paragraph alignment value defaults to left, null not allowed

2025-07-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69720 --- Comment #1 from Jacobo Aragunde Pérez --- For extra confusion, Word uses the "left" value for alignment, while LibreOffice prefers "start". If I re-save the attached test case with Word, both paragraphs would return

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 Axel Howind changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 --- Comment #8 from PJ Fanning --- I would suggest that you install Java 8 and Java 11 if Gradle on Windows can't download Java 11 for you. -- You are receiving this mail because: You are the assignee for th

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 --- Comment #7 from PJ Fanning --- The thing is that Gradle already is configured to do this for you. The OP has not even stated what the issue is. If you read their question on stackoverflow, they are providing little or no evidence of work

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 --- Comment #6 from Dominik Stadler --- I updated the text at https://poi.apache.org/devel/index.html via r1926808 to mention JDK 11. -- You are receiving this mail because: You are the assignee for the bug

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 --- Comment #5 from Axel Howind --- I think you actually do need a Java 9 compiler (for the module info), even when a java 8 compiler is used for the rest. So yes, you technically need a java 9 compiler to build even if the resulting jar will

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 Shilpa BN changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 --- Comment #3 from Shilpa BN --- Created attachment 40052 --> https://bz.apache.org/bugzilla/attachment.cgi?id=40052&action=edit Error screenshot This image contains the command ran against the project and the error received. --

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 --- Comment #2 from PJ Fanning --- POI's Gradle build uses docs.gradle.org/current/userguide/toolchains.html to manage being able to build the module-info classes even if the build is run with Java 8. Basically, Gradle will find on

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 PJ Fanning changed: What|Removed |Added Resolution|--- |INFORMATIONPROVIDED Status

[Bug 69729] Unable to build POI 5.4.1 with JDK 8

2025-06-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 Shilpa BN changed: What|Removed |Added CC||shilpa...@gmail.com OS

[Bug 69729] New: Unable to build POI 5.4.1 with JDK 8

2025-06-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69729 Bug ID: 69729 Summary: Unable to build POI 5.4.1 with JDK 8 Product: POI Version: 5.4.1-FINAL Hardware: PC Status: NEW Severity: critical Priority: P2

[Bug 69727] XSSFSheet Wrong count when call removeMergedRegion and addMergedRegion

2025-06-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69727 Matafagafo changed: What|Removed |Added CC||matafag...@gmail.com OS

[Bug 69726] Error: class CTTblStylePr not found

2025-06-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69726 Jacobo Aragunde Pérez changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution

[Bug 69727] New: XSSFSheet Wrong count when call removeMergedRegion and addMergedRegion

2025-06-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69727 Bug ID: 69727 Summary: XSSFSheet Wrong count when call removeMergedRegion and addMergedRegion Product: POI Version: 5.4.1-FINAL Hardware: PC Status: NEW

[Bug 69726] Error: class CTTblStylePr not found

2025-06-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69726 --- Comment #1 from PJ Fanning --- these "org.openxmlformats.schemas..." classes are in poi-ooxml-lite and poi-ooxml-full jars https://mvnrepository.com/artifact/org.apache.poi/poi-ooxml-lite https://mvnrepository.com/artifact/org.

[Bug 69726] Error: class CTTblStylePr not found

2025-06-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69726 PJ Fanning changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this mail

[Bug 69726] New: Error: class CTTblStylePr not found

2025-06-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69726 Bug ID: 69726 Summary: Error: class CTTblStylePr not found Product: POI Version: 5.4.1-FINAL Hardware: PC OS: Linux Status: NEW Severity: normal

[Bug 69723] New: Self

2025-06-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69723 Bug ID: 69723 Summary: Self Product: POI Version: 5.4.x-dev Hardware: All OS: OpenBSD Status: NEW Severity: major Priority: P2

[Bug 69720] New: Paragraph alignment value defaults to left, null not allowed

2025-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69720 Bug ID: 69720 Summary: Paragraph alignment value defaults to left, null not allowed Product: POI Version: 5.4.x-dev Hardware: PC OS: Linux

[Bug 69718] xval if not specified is giving error instead of taking a default value

2025-06-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69718 --- Comment #2 from PJ Fanning --- Unfortunately, POI is a volunteer project and at this stage, if you want a fix, you are best off considering submitting it yourself. I give this answer all the time - so I have done a doc to summarise the

[Bug 69718] xval if not specified is giving error instead of taking a default value

2025-06-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69718 Matafagafo changed: What|Removed |Added CC||matafag...@gmail.com -- You are

[Bug 69718] xval if not specified is giving error instead of taking a default value

2025-06-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69718 --- Comment #1 from parvathyskumar...@gmail.com --- Created attachment 40050 --> https://bz.apache.org/bugzilla/attachment.cgi?id=40050&action=edit In this attachment K6 is empty but excel evaluates the formula of A1 whereas POI d

[Bug 69718] New: xval if not specified is giving error instead of taking a default value

2025-06-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69718 Bug ID: 69718 Summary: xval if not specified is giving error instead of taking a default value Product: POI Version: 5.4.1-FINAL Hardware: PC OS: Mac OS

[Bug 69697] Error in public HSLFPictureData getPictureData() of class HSLFPictureShape

2025-06-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69697 PJ Fanning changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 69681] Issue with date format ending with ".000 AM/PM" (a date format ending with milliseconds + AM/PM with a space in between).

2025-06-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69681 --- Comment #2 from PJ Fanning --- current fix only allows one optional space before the AM/PM part -- You are receiving this mail because: You are the assignee for the bug

[Bug 69681] Issue with date format ending with ".000 AM/PM" (a date format ending with milliseconds + AM/PM with a space in between).

2025-06-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69681 PJ Fanning changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 69714] Allow custom TempFileCreationStrategy per thread

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 PJ Fanning changed: What|Removed |Added Hardware|PC |All Resolution

[Bug 69714] Allow custom TempFileCreationStrategy per thread

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 PJ Fanning changed: What|Removed |Added Summary|Allow custom|Allow custom

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #10 from PJ Fanning --- I have merged the PR and have tidied up the ThreadLocal to call remove when nulls are in play. -- You are receiving this mail because: You are the assignee for the bug

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #9 from Attila Kelemen --- Some notes on your current implementation: - I cannot restore the strategy of my caller. The simplest change you can do to allow this is to return the previous strategy in

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #8 from Attila Kelemen --- My issue with your implementation is that I cannot restore the previous implementation to avoid changing the strategy to the caller (and also cannot cleanup garbage manually). In the mean time I also

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #7 from PJ Fanning --- I added some changes to TempFile to allow a thread specific strategy. https://github.com/apache/poi/commit/9c08d29fcbd0f3f4fec5f27349246bf6a84fe78a and https://github.com/apache/poi/commit

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #6 from PJ Fanning --- Ok. If the change can be kept to your approx 30 lines, I will review it. -- You are receiving this mail because: You are the assignee for the bug

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #5 from Attila Kelemen --- In fact, I just checked, it is literally just 30 lines of extra code (pretty much trivial) containing one extra public method, with 2 modified lines (replacing `strategy` with `getStrategy()` within

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #4 from Attila Kelemen --- I don't really see how my "middle ground" proposal is a drastic change. It would just declare a thread local, and if the thread local value is set, then would use that strategy. That would

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #3 from PJ Fanning --- I am against big new temp file API changes. You can plug in your own strategy using https://poi.apache.org/apidocs/dev/org/apache/poi/util/TempFile.html#setTempFileCreationStrategy

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 --- Comment #2 from Attila Kelemen --- I think POI's mistaken assumption here is that what uses tmp files and what doesn't is an implementation detail, but tmp file usage has very important implications (mainly security and quota)

[Bug 69714] Allow custom TempFileCreationStrategy per document

2025-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 PJ Fanning changed: What|Removed |Added OS||All --- Comment #1 from PJ Fanning

[Bug 69715] DefaultTempFileCreationStrategy forgets the originally set directory, if it doesn't exist

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69715 --- Comment #6 from Attila Kelemen --- As promised in #823, I have created a PR which fixes this: https://github.com/apache/poi/pull/824 As a side effect, the race conditions in the implementations are also fixed. -- You are receiving this

[Bug 69715] DefaultTempFileCreationStrategy forgets the originally set directory, if it doesn't exist

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69715 --- Comment #5 from PJ Fanning --- The changes I made are https://github.com/apache/poi/commit/c5ca5ae0657250669349304d5a0ddf1f601656a3 and https://github.com/apache/poi/commit/c5df00b0a785d47bea08c4e6d03e4d4c5696b0c3 -- You are receiving

[Bug 69715] DefaultTempFileCreationStrategy forgets the originally set directory, if it doesn't exist

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69715 --- Comment #4 from PJ Fanning --- I repeat that POI is a low level lib. If orgs can't ensure that dirs are not deleted, then they have severe internal problems that I don't care about it. Orgs like this can plug in their own more c

[Bug 69715] DefaultTempFileCreationStrategy forgets the originally set directory, if it doesn't exist

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69715 --- Comment #3 from Attila Kelemen --- It is not just malicious 3rd party though. A directory can be deleted by accident, and then poi will mistakenly start writing to a directory where it was not supposed to. -- You are receiving this mail

[Bug 69715] DefaultTempFileCreationStrategy forgets the originally set directory, if it doesn't exist

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69715 --- Comment #2 from PJ Fanning --- I've added some commits to be strict in the constructor. If you provide a non-null file, it must refer to a directory that already exists. This should stop the scenario where the code will fallback t

[Bug 69715] DefaultTempFileCreationStrategy forgets the originally set directory, if it doesn't exist

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69715 PJ Fanning changed: What|Removed |Added OS||All --- Comment #1 from PJ Fanning

[Bug 69715] New: DefaultTempFileCreationStrategy forgets the originally set directory, if it doesn't exist

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69715 Bug ID: 69715 Summary: DefaultTempFileCreationStrategy forgets the originally set directory, if it doesn't exist Product: POI Version: unspecified Hardwar

[Bug 69714] New: Allow custom TempFileCreationStrategy per document

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69714 Bug ID: 69714 Summary: Allow custom TempFileCreationStrategy per document Product: POI Version: unspecified Hardware: PC Status: NEW Severity: enhancement

[Bug 69697] Error in public HSLFPictureData getPictureData() of class HSLFPictureShape

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69697 --- Comment #2 from PJ Fanning --- I added https://github.com/apache/poi/commit/c01228c331fce2743e1434ebdea31b895615b41d -- You are receiving this mail because: You are the assignee for the bug

[Bug 69688] Exception regarding formulas thrown when using HSSFRow copyRowFrom method even though data has no formulas

2025-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69688 PJ Fanning changed: What|Removed |Added Status|NEW |RESOLVED Resolution

  1   2   3   4   5   6   7   8   9   10   >