[GitHub] [commons-net] jkbkupczyk commented on pull request #162: Add FTPFile tests and fix javadoc typos

2023-07-04 Thread via GitHub
jkbkupczyk commented on PR #162: URL: https://github.com/apache/commons-net/pull/162#issuecomment-1621046327 @garydgregory done Thought it looked kinda odd to have the `read` method before setters. But it makes sense to have them sorted :) -- This is an automated message from the

Re: [jira] [Deleted] (LANG-1647) Add and ExceptionUtils.isChecked() and isUnchecked()

2023-07-04 Thread sebb
Sorry, but that does not answer my question as to why the ticket was deleted rather than just being closed (e.g. as a duplicate)? A closed ticket does not involve any work, otherwise why don't we delete all closed tickets? Whereas a deleted ticket that is referred to in various place does cause

[GitHub] [commons-net] jkbkupczyk opened a new pull request, #162: Add FTPFile tests and fix javadoc typos

2023-07-04 Thread via GitHub
jkbkupczyk opened a new pull request, #162: URL: https://github.com/apache/commons-net/pull/162 - Fixed some typos in Javadoc and adjusted documentation to code - Replaced HTML snippets with Javadoc counterparts - Moved serialization-related methods under the "serialization comment"

Re: [jira] [Deleted] (LANG-1647) Add and ExceptionUtils.isChecked() and isUnchecked()

2023-07-04 Thread Gary Gregory
Because it doubles up the work form the original ticket. We do not need a second ticket to track the same new feature IMO. Gary On Tue, Jul 4, 2023, 12:57 sebb wrote: > Why did you delete this ticket? > > It is referred to in various emails and commit messages, so it is > confusing that the

Re: [jira] [Deleted] (LANG-1647) Add and ExceptionUtils.isChecked() and isUnchecked()

2023-07-04 Thread sebb
Why did you delete this ticket? It is referred to in various emails and commit messages, so it is confusing that the ticket does not exist. I think only tickets which are spam should be deleted. Sebb On Mon, 3 Jul 2023 at 12:04, Gary D. Gregory (Jira) wrote: > > > [ >

[jira] [Commented] (DAEMON-460) High CPU usage in prunsrv.exe since Daemon 1.3.3

2023-07-04 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/DAEMON-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739918#comment-17739918 ] Gary D. Gregory commented on DAEMON-460: I don't have anything. You might want to try and see

[jira] [Comment Edited] (IMAGING-356) TIFF reading extremely slow in version 1.0-SNAPSHOT

2023-07-04 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/IMAGING-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739916#comment-17739916 ] Gary D. Gregory edited comment on IMAGING-356 at 7/4/23 1:00 PM: - Hi

[jira] [Commented] (IMAGING-356) TIFF reading extremely slow in version 1.0-SNAPSHOT

2023-07-04 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/IMAGING-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739916#comment-17739916 ] Gary D. Gregory commented on IMAGING-356: - Hi [~gwlucas] After looking at VisualVM (see

[jira] [Commented] (DAEMON-460) High CPU usage in prunsrv.exe since Daemon 1.3.3

2023-07-04 Thread Japie vd Linde (Jira)
[ https://issues.apache.org/jira/browse/DAEMON-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739913#comment-17739913 ] Japie vd Linde commented on DAEMON-460: --- Hi, just wanted to check if there is any additional

[jira] [Updated] (IMAGING-356) TIFF reading extremely slow in version 1.0-SNAPSHOT

2023-07-04 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/IMAGING-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated IMAGING-356: Attachment: image-2023-07-04-08-52-36-535.png > TIFF reading extremely slow in version

[jira] [Resolved] (EXEC-53) Allow control over asynchronous execution thread

2023-07-04 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/EXEC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved EXEC-53. - Fix Version/s: 1.2 Resolution: Fixed > Allow control over asynchronous execution thread >

[jira] [Commented] (EXEC-53) Allow control over asynchronous execution thread

2023-07-04 Thread Nikolay Martynov (Jira)
[ https://issues.apache.org/jira/browse/EXEC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739875#comment-17739875 ] Nikolay Martynov commented on EXEC-53: -- Yes, I think

[GitHub] [commons-lang] aherbert commented on a diff in pull request #1062: Syntax for optional tokens in DurationFormatUtils

2023-07-04 Thread via GitHub
aherbert commented on code in PR #1062: URL: https://github.com/apache/commons-lang/pull/1062#discussion_r1251780977 ## src/main/java/org/apache/commons/lang3/time/DurationFormatUtils.java: ## @@ -48,6 +48,13 @@ * Token values are printed using decimal digits. * A token

[jira] [Updated] (COLLECTIONS-843) Add LayeredBloomFilter

2023-07-04 Thread Claude Warren (Jira)
[ https://issues.apache.org/jira/browse/COLLECTIONS-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren updated COLLECTIONS-843: -- Description: Add a Layered Bloom filter implementation along the lines described