[
https://issues.apache.org/jira/browse/MRESOLVER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693977#comment-17693977
]
ASF GitHub Bot commented on MRESOLVER-329:
------------------------------------------
cstamas opened a new pull request, #260:
URL: https://github.com/apache/maven-resolver/pull/260
In case of concurrent r/w of tracking file, the if Files.isReablable may
return true, but the file might be gone once it arrives to
Files.newInputStream. In these cases, just ignore the missing file related
exception.
---
https://issues.apache.org/jira/browse/MRESOLVER-329
> Make IO in DefaultTrackingFileManager more robust
> -------------------------------------------------
>
> Key: MRESOLVER-329
> URL: https://issues.apache.org/jira/browse/MRESOLVER-329
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.6
>
>
> There are couple of spots where implementation naively assumes is alone
> running process on this world. Several user reports suggests this is not the
> case, like MRESOLVER-325 or MNG-7705. Fix these spots.
> Still, something is fishy, as it seems these files (all that are handled by
> DefaultTrackingFileManager) are not subject to locking? This needs
> investigation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
