-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.nio.file.AccessDeniedExceptions for ORT Versions 31+ on MS Windows #9334
Comments
@randygeyer, as you seem to be running into this as well, would you be able to assist with debugging this? Like finding out what's probably locking the I'm not in favor of just reverting a477ded as that would reintroduce #8987. |
@sschuberth I'll look into it as I have reproduced this in my own unrelated code that also uses jgit and However, I won't have cycles for this for a week or two, and this is a critical blocker for me. How can I work around this in the meantime? Is there an alternative |
Please give #9348 a try.
No. |
Note to myself: With |
So the problem is that files within |
Interesting that File.deleteRecursively() ignores that. Any estimate on a release date for either the .recover workaround or the fix? |
We do weekly releases on Thursdays. I'm confident that a fix makes it into it. |
Fixes #9334. Signed-off-by: Sebastian Schuberth <[email protected]>
Fixes #9334. Signed-off-by: Sebastian Schuberth <[email protected]>
Fixes #9334. Signed-off-by: Sebastian Schuberth <[email protected]>
Slightly align the wording of code comments while at it. Fixes #9334. Signed-off-by: Sebastian Schuberth <[email protected]>
Slightly align the wording of code comments while at it. Fixes #9334. Signed-off-by: Sebastian Schuberth <[email protected]>
Describe the bug
Any ORT Version starting with 31.0.0, running on MS Windows 10, result in a java.nio.file.AccessDeniedException when using the scanner.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Scan will finish successfully.
Console / log output
Environment
Output of the
ort requirements -l commands
command:Or manually specify:
And specify (relevant parts of) your ORT configuration (
config.yml
):Additional context
According to sschuberth, the bug might be caused by the changes in commit:
a477ded
The text was updated successfully, but these errors were encountered: