You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Jason Shattu (JIRA)" <ji...@apache.org> on 2017/04/10 11:16:41 UTC

[jira] [Updated] (COMPRESS-384) Tar File EOF not being detected

     [ https://issues.apache.org/jira/browse/COMPRESS-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Shattu updated COMPRESS-384:
----------------------------------
    Description: 
I've created both a zip and tar file, with the same contents using the latest version of 7zip. When I read both archives using code of the form:

ArchiveStreamFactory().createArchiveInputStream(format, inputStream);

I notice that both formats correctly list their contents, however the Tar Input doesn't return a "null" entry when it hits the EOF from archiveStream.getNextEntry() 

this makes it hard to distinguish between a genuine EOF or a file which is still being written to. 


  was:
I've created both a zip and tar file, with the same contents using the latest version of 7zip. When I read both archives using code of the form:

ArchiveStreamFactory().createArchiveInputStream(format, inputStream);

I notice that both formats correctly list their contents, however the Tar Input does't return a "null" entry when it hits the EOF from archiveStream.getNextEntry() 

this makes it hard to distinguish between a genuine EOF or a file which is still being written to. 



> Tar File EOF not being detected
> -------------------------------
>
>                 Key: COMPRESS-384
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-384
>             Project: Commons Compress
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.13
>         Environment: Windows 10, JDK 1.8
>            Reporter: Jason Shattu
>
> I've created both a zip and tar file, with the same contents using the latest version of 7zip. When I read both archives using code of the form:
> ArchiveStreamFactory().createArchiveInputStream(format, inputStream);
> I notice that both formats correctly list their contents, however the Tar Input doesn't return a "null" entry when it hits the EOF from archiveStream.getNextEntry() 
> this makes it hard to distinguish between a genuine EOF or a file which is still being written to. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)