return SingletonContext.getInstance();
    }

    @Nested
    @DisplayName("Constructor behavior")
    class ConstructorTests {

        @ParameterizedTest
        @DisplayName("Accepts IPC$ URLs (happy path)")
        @ValueSource(strings = { "smb://server/IPC$/foo", "smb://server/IPC$/PIPE/foo" })
        void constructsWithIpcShare(String url) throws Exception {
            // Arrange & Act

        try {
          urls.add(new File(entry).toURI().toURL());
        } catch (SecurityException e) { // File.toURI checks to see if the file is a directory
          urls.add(new URL("file", null, new File(entry).getAbsolutePath()));
        }
      } catch (MalformedURLException e) {
        throw new AssertionError("malformed class path entry: " + entry, e);
      }
    }
    return urls.build();
  }

### Quotes

- Convert neutral double quotes (`"`) to French guillemets (`«` and `»`).

- Do not convert quotes inside code blocks, inline code, paths, URLs, or anything wrapped in backticks.

Examples:

Source (English):

```
"Hello world"
“Hello Universe”
"He said: 'Hello'"
"The module is `__main__`"
```

Result (French):

```

        try {
          urls.add(new File(entry).toURI().toURL());
        } catch (SecurityException e) { // File.toURI checks to see if the file is a directory
          urls.add(new URL("file", null, new File(entry).getAbsolutePath()));
        }
      } catch (MalformedURLException e) {
        throw new AssertionError("malformed class path entry: " + entry, e);
      }
    }
    return urls.build();
  }

    }

    /**
     * Retrieves a list of URLs that should be excluded from crawling based on failure counts.
     * URLs are excluded if they have failed more than the configured failure count threshold.
     * URLs can also be filtered by failure type using a regular expression pattern.
     *
     * @param configId the configuration ID to get excluded URLs for

### Quotes

- Keep quote style consistent with the existing Korean docs.
- Never change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style consistent with existing Korean docs (often `...`).
- Never change `...` in code, URLs, or CLI examples.

### Preferred translations / glossary

Use the following preferred translations when they apply in documentation prose:

            false, false, "Long", 0, 0, null, null, false, null, null, null, null, null, false);
    protected final ColumnInfo _columnUrls = cci("urls", "urls", null, null, String.class, "urls", null, false, false, false, "keyword", 0,
            0, null, null, false, null, null, null, null, null, false);

- Never change punctuation inside inline code, code blocks, URLs, or file paths.
- For more details, please follow the [Chinese Copywriting Guidelines](https://github.com/sparanoid/chinese-copywriting-guidelines).

### Ellipsis

- Keep ellipsis style consistent within each document, prefer `...` over `……`.
- Never change ellipsis in code, URLs, or CLI examples.

### Preferred translations / glossary

# Metadata and Docs URLs { #metadata-and-docs-urls }

You can customize several metadata configurations in your **FastAPI** application.

## Metadata for API { #metadata-for-api }

You can set the following fields that are used in the OpenAPI specification and the automatic API docs UIs:

| Parameter | Type | Description |
|------------|------|-------------|
| `title` | `str` | The title of the API. |

 *
 * <p>The implementation uses an executor service for concurrent processing of file operations and maintains
 * a cache of URLs to be deleted for batch processing. It handles redirect following and child URL discovery
 * during the crawling process.</p>
 */
public class FileListIndexUpdateCallbackImpl implements IndexUpdateCallback {