[GitHub] [poi] FlyingPigQAQ commented on pull request #371: fix: when copy slide,new slide use old textrun object reference

FlyingPigQAQ commented on PR #371: URL: https://github.com/apache/poi/pull/371#issuecomment-1220181755 Unit tests were added. -- 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.

Jenkins build is back to normal : POI » POI-XMLBeans-DSL-1.8 #165

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

[Bug 66229] i need date,but i wirte too long integer insert sucessed

https://bz.apache.org/bugzilla/show_bug.cgi?id=66229 --- Comment #2 from puguoan --- getCellDate(): xls/xlsx file cell value = "" i read file,use getCellDate() get value.that is date type. --- DataFormatter: cell = "2022/02/02" or "111" i try use DataFormatter.formatCellV

[Bug 65473] when do copy slide operation, text shape's copy is not working, new slide use the old text shape object's reference

https://bz.apache.org/bugzilla/show_bug.cgi?id=65473 --- Comment #3 from PJ Fanning --- See https://github.com/apache/poi/pull/371 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-ma

[GitHub] [poi] FlyingPigQAQ commented on pull request #371: fix: when copy slide,new slide use old textrun object reference

FlyingPigQAQ commented on PR #371: URL: https://github.com/apache/poi/pull/371#issuecomment-1220122256 > It is also better to raise a bug first before providing PRs. See https://bz.apache.org/bugzilla Hello, I read the buglist and found an issue with the same problem but not fixed. T

Build failed in Jenkins: POI » POI-XMLBeans-DSL-1.8 #164

See Changes: [PJ Fanning] some int narrowing -- [...truncated 634.92 KB...] created source:

[GitHub] [poi] pjfanning commented on pull request #371: fix: when copy slide,new slide use old textrun object reference

pjfanning commented on PR #371: URL: https://github.com/apache/poi/pull/371#issuecomment-1220107861 It is also better to raise a bug first before providing PRs. See https://bz.apache.org/bugzilla -- This is an automated message from the Apache Git Service. To respond to the message, pleas

[GitHub] [poi] pjfanning commented on pull request #371: fix: when copy slide,new slide use old textrun object reference

pjfanning commented on PR #371: URL: https://github.com/apache/poi/pull/371#issuecomment-1220107451 Please provide some description - and ideally a test case to go with this. It is not enough to modify code without describing why. -- This is an automated message from the Apache Git Servic

[Bug 66216] XSSFPivotTable.getPivotCacheDefinition() does not work properly when XSSFPivotTable was read from an existing *.xlsx file

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

[Bug 66215] Versions greater than 5.1 damages structured references while XSSFsheet.shiftRows

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

[Bug 66230] SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

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

Re: [VOTE] Apache XmlBeans 5.1.1 release (RC1)

I didn't see the Github PR linked to  https://issues.apache.org/jira/browse/XMLBEANS-623 I think it's probably worth cancelling RC1 and doing an RC2 to get that in. I'll how the CI build works out and prep a new RC if it goes smoothly. This will also drag in https://issues.apache.org/jira/browse

[jira] [Created] (XMLBEANS-623) Hardening of zip slip check in JarHelper

PJ Fanning created XMLBEANS-623: --- Summary: Hardening of zip slip check in JarHelper Key: XMLBEANS-623 URL: https://issues.apache.org/jira/browse/XMLBEANS-623 Project: XMLBeans Issue Type: Impro

[Bug 66230] SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

https://bz.apache.org/bugzilla/show_bug.cgi?id=66230 --- Comment #7 from Patric Rufflar --- Ok, so it's safe to continue with the worksheet on which setAutoSizeColumn() failed. Thanks for your effort! -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 66230] SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

https://bz.apache.org/bugzilla/show_bug.cgi?id=66230 --- Comment #6 from PJ Fanning --- autoSizeColumn method will fail if the auto size tracker has not initialized - an IllegalStateException - it's up to you how to handle this -- You are receiving this mail because: You are the assignee for th

[Bug 66230] SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

https://bz.apache.org/bugzilla/show_bug.cgi?id=66230 --- Comment #5 from Patric Rufflar --- Thanks for your quick response and fix! First of all a fix in 5.2.x would be fine for me - thanks! 1. I agree - at least avoiding the NPE when not using auto-size at all is the minimum we should do. 2.

[Bug 66230] SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

https://bz.apache.org/bugzilla/show_bug.cgi?id=66230 --- Comment #4 from PJ Fanning --- I added r1903529 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.ap

[Bug 66230] SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

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

[Bug 66230] SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

https://bz.apache.org/bugzilla/show_bug.cgi?id=66230 --- Comment #2 from PJ Fanning --- PS We don't support POI 3.17. If we made changes, it would be in POI 5.2.x. -- You are receiving this mail because: You are the assignee for the bug. -

[Bug 66230] SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

https://bz.apache.org/bugzilla/show_bug.cgi?id=66230 PJ Fanning changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from PJ Fanning

[Bug 66230] New: SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing

https://bz.apache.org/bugzilla/show_bug.cgi?id=66230 Bug ID: 66230 Summary: SheetUtil.getDefaultCharWidth() should handle AWT NPE instead of failing Product: POI Version: unspecified Hardware: PC OS: Linux

[jira] [Commented] (XMLBEANS-622) javaparser 3.24.4 breaks xmlbeans build

[ https://issues.apache.org/jira/browse/XMLBEANS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581421#comment-17581421 ] PJ Fanning commented on XMLBEANS-622: - This gets stranger still. If I run with java

[jira] [Commented] (XMLBEANS-622) javaparser 3.24.4 breaks xmlbeans build

[ https://issues.apache.org/jira/browse/XMLBEANS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581411#comment-17581411 ] PJ Fanning commented on XMLBEANS-622: - I get the correct names of the files and cla

Re: Migrate from Bugzilla to GitHub Issues

ASF projects must store source and source releases on ASF controlled properties. A significant amount of work has been done in the last decade to connect Gitbox with GitHub. If anyone personally has trouble with Microsoft’s owning GitHub they can use the gitbox mirrors. 14 years ago we had sig

Re: Migrate from Bugzilla to GitHub Issues

>2. What will happen to the mail list archives with links to Bugzilla ? >Will it possible to redirect Bugzilla urls to the migrated GitHub Issues? I have not explored the possibility to install automatic redirects, however, for JMeter we'll add a comment to every bug that links the corresponding

Re: Migrate from Bugzilla to GitHub Issues

GitHub is cool and personally, I much prefer GitHub PRs to Bugzilla. There are two questions though: 1. Github is Apache-friendly, but it is not owned by ASF. For whatever reasons they can change their policy, access, etc. and we won't have control over it. It's hypothetical, but who knows? 2. Wh

Re: Migrate from Bugzilla to GitHub Issues

Dear all, When considering a move like this, you might like to also consider alternatives to GitHub. I am not going to argue strongly for one service over another, but just note that there is continuing sensitivity for some over Microsoft's policies with respect to GitHub. The Software Freedo

[jira] [Commented] (XMLBEANS-622) javaparser 3.24.4 breaks xmlbeans build

[ https://issues.apache.org/jira/browse/XMLBEANS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581305#comment-17581305 ] Peter Keller commented on XMLBEANS-622: --- Some time ago, I used to develop jointly

Re: Migrate from Bugzilla to GitHub Issues

Thanks Vladimir for bringing this up. I think it would be a good idea to have a discussion on this list before anyone dedicates too much effort. My own opinion is that it would be great to get off bugzilla. I see the merit in using Github instead of Jira - because Github is an integrated environ

[Bug 66229] i need date,but i wirte too long integer insert sucessed

https://bz.apache.org/bugzilla/show_bug.cgi?id=66229 PJ Fanning changed: What|Removed |Added OS||All Status|NEW

[jira] [Commented] (XMLBEANS-622) javaparser 3.24.4 breaks xmlbeans build

[ https://issues.apache.org/jira/browse/XMLBEANS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581287#comment-17581287 ] PJ Fanning commented on XMLBEANS-622: - Even a fresh checkout on my Mac runs into sa

[jira] [Commented] (XMLBEANS-622) javaparser 3.24.4 breaks xmlbeans build

[ https://issues.apache.org/jira/browse/XMLBEANS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581282#comment-17581282 ] PJ Fanning commented on XMLBEANS-622: - xmlbeans won't build on my Mac when javapars

[jira] [Updated] (XMLBEANS-622) javaparser 3.24.4 breaks xmlbeans build

[ https://issues.apache.org/jira/browse/XMLBEANS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PJ Fanning updated XMLBEANS-622: Fix Version/s: Version 5.1.2 > javaparser 3.24.4 breaks xmlbeans build >

[jira] [Commented] (XMLBEANS-622) javaparser 3.24.4 breaks xmlbeans build

[ https://issues.apache.org/jira/browse/XMLBEANS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581263#comment-17581263 ] Peter Keller commented on XMLBEANS-622: --- I'd be interested in taking a closer loo

Re: Migrate from Bugzilla to GitHub Issues

Just in case, I can prepare a throwaway repository with migrated issues/attachments for POI. I would need an export from Bugzilla database for POI issues. You could ask it from INFRA like in https://issues.apache.org/jira/browse/INFRA-23475. >Do you have examples of successful transition from Bugz

Re: Migrate from Bugzilla to GitHub Issues

Hi, Vladimir, Do you have examples of successful transition from Bugzilla to GitHub issues for Apache projects? (already completed ones) Best regards, Sergey Чт, 18 авг. 2022 г. в 08:11, Vladimir Sitnikov : > Hi, > > Have you considered migrating from Bugzilla to GitHub Issues? > > I think co-l