Community
Participate
Working Groups
The following problem was reported via the automated error reporting: Message: Error java.nio.file.AccessDeniedException: C:\Users\Mina Emil at sun.nio.fs.WindowsException.translateToIOException(null:-1) at sun.nio.fs.WindowsException.rethrowAsIOException(null:-1) at sun.nio.fs.WindowsException.rethrowAsIOException(null:-1) at sun.nio.fs.WindowsFileSystemProvider.createDirectory(null:-1) at java.nio.file.Files.createDirectory(null:-1) at java.nio.file.Files.createAndCheckIsDirectory(null:-1) at java.nio.file.Files.createDirectories(null:-1) at org.eclipse.core.internal.filesystem.local.LocalFile.mkdir(LocalFile.java:307) at org.eclipse.cdt.internal.ui.buildconsole.BuildConsolePartitioner.logOpen(BuildConsolePartitioner.java:183) at org.eclipse.cdt.internal.ui.buildconsole.BuildConsolePartitioner.setStreamOpened(BuildConsolePartitioner.java:129) at org.eclipse.cdt.internal.ui.buildconsole.BuildOutputStream.<init>(BuildOutputStream.java:40) at org.eclipse.cdt.internal.ui.buildconsole.BuildConsolePartitioner.getOutputStream(BuildConsolePartitioner.java:464) at org.eclipse.cdt.internal.ui.buildconsole.MultiBuildConsoleAdapter.getOutputStream(MultiBuildConsoleAdapter.java:99) at org.eclipse.cdt.internal.ui.buildconsole.CBuildConsole.getOutputStream(CBuildConsole.java:72) at org.eclipse.cdt.internal.core.BuildRunnerHelper.prepareStreams(BuildRunnerHelper.java:142) at org.eclipse.cdt.managedbuilder.core.InternalBuildRunner.invokeBuild(InternalBuildRunner.java:102) at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:753) at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:510) at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:459) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:487) at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:399) Bundles: | org.eclipse.cdt.core | 6.3.1.201706122201 | 6.3.1.201706122201 | | org.eclipse.cdt.managedbuilder.core | 8.5.0.201706122201 | 8.5.0.201706122201 | | org.eclipse.cdt.ui | 6.2.0.201706122201 | 6.2.0.201706122201 | | org.eclipse.core.filesystem | 1.7.0.v20170406-1337 | 1.7.0.v20170406-1337 | | org.eclipse.core.resources | 3.12.0.v20170417-1558 | 3.12.0.v20170417-1558 | | org.eclipse.core.runtime | 3.13.0.v20170207-1030 | 3.13.0.v20170207-1030 | Operating Systems: | Windows | 10.0.0 | 10.0.0 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5992a9f7e4b07a83ba4421bd for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. Created on behalf of zeratul976@xxxxxx.xxx
cc'ing Jonah as he has made changes to BuildConsolePartitioner recently.
(In reply to Nathan Ridge from comment #1) > cc'ing Jonah as he has made changes to BuildConsolePartitioner recently. Thanks Nathan. I think that this problem is a user error, but I need to experiment to see if this error is displayed to user in any sensible way, and to ensure that opening the log file can fail without breaking other stuff. Assigning for 9.3.2 until I can confirm this error does not break other stuff. If it does not break other stuff it will become a 9.4.0 bug.
(In reply to Jonah Graham from comment #2) > I think that this problem is a user error, but I need to experiment to see > if this error is displayed to user in any sensible way, and to ensure that > opening the log file can fail without breaking other stuff. This is indeed a user error. For 9.4 to consider how to display better to user. > Assigning for 9.3.2 until I can confirm this error does not break other > stuff. If it does not break other stuff it will become a 9.4.0 bug.
(In reply to Jonah Graham from comment #3) > This is indeed a user error. For 9.4 to consider how to display better to > user. I think this is a perfect place to use something like Mylyn notifications -- there was talk about migrating that to the platform
This is user error, I haven't so far found time to dedicate anytime to figuring out how to restructure this. My more recent idea is to create a problem marker for the user error here rather than a pop-up/mylyn style one. Similar to how other CDT config error happen.
Maybe this can help http://www.codersmagazine.com/java-accessdeniedexception-java-nio-file-accessdeniedexception/
(In reply to Mariksel Azemaj from comment #6) > Maybe this can help > http://www.codersmagazine.com/java-accessdeniedexception-java-nio-file- > accessdeniedexception/ Hi Mariksel, Thanks for the link. That is along the line of what is wrong. At the moment this bug is to deal with how to expose this error to the user, rather than simply logging it to the log file. This error should only happen when a user has entered an invalid file (permission denied, a directory, or something else). The probable place to display this is as an error marker in the Problems view. Do you have any experience in this area? I would be happy to work with you to get this problem resolved. Thanks! Jonah
