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

[ASF GitHub Bot (Jira)]

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

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

                Author: ASF GitHub Bot
            Created on: 27/Jan/21 23:20
            Start Date: 27/Jan/21 23:20
    Worklog Time Spent: 10m 
      Work Description: coveralls commented on pull request #192:
URL: https://github.com/apache/commons-io/pull/192#issuecomment-768642694


   
   [![Coverage 
Status](https://coveralls.io/builds/36650052/badge)](https://coveralls.io/builds/36650052)
   
   Coverage decreased (-0.1%) to 89.092% when pulling 
**a559f8a99d97a996b9ecba48680ed04588205ce6 on boris-unckel:assert_proposal** 
into **5f73593d999feccc93f6e8190af22d52726bba14 on apache: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.

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


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

    Worklog Id:     (was: 543178)
    Time Spent: 50m  (was: 40m)

> 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: 50m
>  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)