[jira] [Work logged] (IO-707) Add optional early error detection as postcondition check

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IO-707?focusedWorklogId=654571&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-654571 ]

ASF GitHub Bot logged work on IO-707:
-------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Sep/21 15:03
            Start Date: 23/Sep/21 15:03
    Worklog Time Spent: 10m 
      Work Description: garydgregory commented on pull request #192:
URL: https://github.com/apache/commons-io/pull/192#issuecomment-925899550


   Hi @boris-unckel and All:
   A lot of time has passed since we last iterated on this issue...
   May you please rebase on master if this is still relevant with master?
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 654571)
    Time Spent: 2h  (was: 1h 50m)

> Add optional early error detection as postcondition check
> ---------------------------------------------------------
>
>                 Key: IO-707
>                 URL: https://issues.apache.org/jira/browse/IO-707
>             Project: Commons IO
>          Issue Type: Improvement
>          Components: Utilities
>    Affects Versions: 2.8.0
>            Reporter: Boris Unckel
>            Priority: Major
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> The current version does not include an optional way to detect errors with the underlying filesystem and/or logic early.
> Due to performance reason and/or design decision, the result of delete or create directories/files does not include a check wheter the delete or create was successful. It "only" relies on trust to the underlying operations of the JDK and/or the completeness of own unit tests.
> To have the option to check things, without having additional commons-io proprietary options and without a performance impact for regular operations the Java 1.4 keyword "assert" should be used.
> Current project profits in case of detail analysis. Downstream projects having own unit tests for IO will profit.
> PR with proposal will follow.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)