[Win32] Folder becomes a file in the workspace tree when a child is deleted during `refreshLocal` (regression in 2026-09)
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 15/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- java
- Ambito
- operating-systems
Direzione di ricerca
Start with Win32Handler.fetchFileInfo and the listDirectoryAndGetFileInfos override, then LocalFile.childInfos and LocalFile.fetchInfo, to see where the name is left unset when a child disappears. Pull request #3025 already targets this, so review it before touching code. Done means the race test RefreshRaceTest no longer yields an empty-name entry and refreshLocal keeps the folder a folder.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Description
Since Eclipse 2026-09 (org.eclipse.core.filesystem 1.11.500), IResource#refreshLocal can turn an existing folder into an IFile in the workspace tree. This happens when one of the folder's children is deleted while the refresh is listing it. On disk the folder is still a directory, but the workspace treats it as a file. After that, creating anything below it fails:
org.eclipse.core.internal.resources.ResourceException: Resource '/P/work' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists
at org.eclipse.core.internal.resources.Folder.assertCreateRequirements
at org.eclipse.core.internal.resources.Folder.create
If the race happens directly below the project, AssertionFailedException: Path must include project and resource name is thrown instead.
With auto-refresh enabled, the refresh monitor usually turns the file back into a folder (fileToFolder) a little later. That makes the failure flaky.
Root cause
LocalFile.childInfos()now goes throughLocalFileNativesManager.listDirectoryAndGetFileInfos→NativeHandler.listDirectoryAndGetFileInfos(introduced in #2787). It gets the names fromFile.list()and then callsfetchFileInfo(dir + File.separator + name)for each one.- If a child is deleted between
File.list()and the native lookup,Win32Handler.fetchFileInfo(FindFirstFileW→ERROR_FILE_NOT_FOUND) returns aFileInfowith an empty name,exists=falseand no error code. Unlike the old code path (FileStore.childInfos→LocalFile.fetchInfo), the name is never filled in. - During
refreshLocal:UnifiedTree.getLocalListsorts the""entry first.createChildNodeFromFileSystemappends""to the parent path, which produces a file node at the folder's own path.RefreshLocalVisitor.synchronizeExistencesees a gender variant, andsynchronizeGendercallsfolderToFile.
The Win32Handler override of listDirectoryAndGetFileInfos added in #2952 has the same flaw: it also leaves the name unset on NoSuchFileException.
Suggested fix
The other implementations of NativeHandler.fetchFileInfo(String) all seem to ensure that the returned fileinfo has a filename set, only the Win32Handler does not seem to have such a case and relies on the callers of fetchFileInfo (e.g. LocalFile.fetchInfo(int, IProgressMonitor) to fix this. So maybe we should also make sure the Win32Handler always sets name?
Steps to reproduce
Windows only. The following JUnit 5 test fails reliably within the first few attempts. Test 1 checks the filesystem layer only. Test 2 shows the symptom through the Workspace API.
package org.eclipse.core.tests.filesystem;
import java.nio.file.Files;
import java.nio.file.Path;
import java.util.ArrayList;
import java.util.List;
import org.eclipse.core.filesystem.EFS;
import org.eclipse.core.filesystem.IFileInfo;
import org.eclipse.core.filesystem.IFileStore;
import org.eclipse.core.resources.IFolder;
import org.eclipse.core.resources.IProject;
import org.eclipse.core.resources.IResource;
import org.eclipse.core.resources.ResourcesPlugin;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.core.runtime.preferences.IEclipsePreferences;
import org.eclipse.core.runtime.preferences.InstanceScope;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.Assertions;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.io.TempDir;
class RefreshRaceTest {
@TempDir
Path tempDir;
IProject project;
@AfterEach
void afterEach() throws Exception {
if (project != null) {
project.delete(true, true, null);
setAutoRefresh(true);
}
}
@Test
void childInfosNeverReturnsNamelessEntry() throws Exception {
IFileStore store = EFS.getLocalFileSystem().getStore(tempDir.toUri());
race(tempDir, () -> {
for (IFileInfo info : store.childInfos(EFS.NONE, null)) {
Assertions.assertFalse(info.getName().isEmpty(), "entry with empty name: " + info);
}
});
}
@Test
void refreshLocalKeepsFolderAFolder() throws Exception {
setAutoRefresh(false); // the refresh monitor would undo the damage
project = ResourcesPlugin.getWorkspace().getRoot().getProject("P");
project.create(null);
project.open(null);
IFolder folder = project.getFolder("work");
folder.create(true, true, null);
race(folder.getLocation().toPath(), () -> {
project.refreshLocal(IResource.DEPTH_INFINITE, null);
Assertions.assertInstanceOf(IFolder.class, project.findMember("work"));
});
folder.getFolder("data").create(true, true, null);
}
/** Fills dir with files and runs probe while another thread deletes them. */
static void race(Path dir, Probe probe) throws Exception {
for (int attempt = 0; attempt < 20; attempt++) {
List<Path> files = new ArrayList<>();
for (int i = 0; i < 2000; i++) {
files.add(Files.createFile(dir.resolve("file" + i + ".tmp")));
}
Thread deleter = new Thread(() -> files.forEach(f -> f.toFile().delete()));
deleter.start();
while (deleter.isAlive()) {
probe.run();
}
deleter.join();
}
}
static void setAutoRefresh(boolean value) throws Exception {
IEclipsePreferences prefs = InstanceScope.INSTANCE.getNode(ResourcesPlugin.PI_RESOURCES);
prefs.putBoolean(ResourcesPlugin.PREF_AUTO_REFRESH, value);
prefs.flush();
}
interface Probe {
void run() throws CoreException;
}
}
Failures observed:
entry with empty name: FileInfo [name=, length=0, lastModified=0, exists=false, attributes=12582912, errorCode=0]
expected: <org.eclipse.core.resources.IFolder> but was: <org.eclipse.core.internal.resources.File>
Disclaimer: I had Claude write this up but debugged most of it manually.
Overall I think that the temporary corruption of the resource tree is a quite a nasty bug.
/cc @HannesWell @iloveeclipse
- Lingua principale
- Java
- Stelle
- 165
- Fork
- 174
- Merge medio
- 3g 6h
- PR unite (30g)
- 44
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di eclipse-platform/eclipse.platform
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
eclipse-platform/eclipse.platform#3019 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
eclipse-platform/eclipse.platform#2940 ·
I maintainer di solito rispondono entro 1 giorno
-
Terminal views all show same name 'Terminal' in Ctrl+F7 view switcher popupForse già presa @ravnskjaer l’ha presa 8 giorni fa. Apertabug good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
eclipse-platform/eclipse.platform#2774 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
eclipse-platform/eclipse.platform#2593 · 7 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
eclipse-platform/eclipse.platform#3027 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di eclipse-platform/eclipse.platform
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
apache/rocketmq-dashboard#6896 ·
I maintainer di solito rispondono entro 3 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
OpenIntegrationEngine/engine#496 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
SasanLabs/VulnerableApp#836 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement frontend
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
Albertinesilva/backend-engineering-journey-java-springboot#46 ·