@BeforeEach
    public void setUp() throws Exception {
        masterPassword = "MasterPassword123!@#".toCharArray();
        storage = new SecureCredentialStorage(masterPassword.clone());
    }

    @AfterEach
    public void tearDown() throws Exception {
        if (storage != null && !storage.isDestroyed()) {
            try {
                storage.close();
            } catch (Exception e) {

 * credentials are retrieved from the {@code jcifs.smb.client.domain},
 * {@code jcifs.smb.client.username}, and {@code jcifs.smb.client.password}
 * properties.
 * <p>
 * Read <a href="../../../authhandler.html">jCIFS Exceptions and
 * NtlmAuthenticator</a> for related information.
 *
 * @deprecated use {@link NtlmPasswordAuthenticator} instead
 */
@Deprecated
public class NtlmPasswordAuthentication extends NtlmPasswordAuthenticator {

   * @throws Exception if unable to load the result
   * @throws InterruptedException if this method is interrupted. {@code InterruptedException} is
   *     treated like any other {@code Exception} in all respects except that, when it is caught,
   *     the thread's interrupt status is set
   */
  public abstract V load(K key) throws Exception;

  /**

- Reference (Code API):
  - reference/index.md
  - reference/fastapi.md
  - reference/parameters.md
  - reference/status.md
  - reference/uploadfile.md
  - reference/exceptions.md
  - reference/dependencies.md
  - reference/apirouter.md
  - reference/background.md
  - reference/request.md
  - reference/websockets.md
  - reference/httpconnection.md
  - reference/response.md

### New properties in an existing class

When adding a property to an existing class (task, extension, domain object, etc), the API should consist of managed lazy properties.  However, some exceptions need to be made to keep backwards compatibility with existing builds.

This is preferred when the implementation type is internal:

```groovy
public interface ExistingThing {
    String getOtherProperty()

 * the maximum number of duplicated paths to attempt, and the character set for encoding the file path.
 * </p>
 *
 * <p>
 * It handles potential exceptions during file creation and storage, throwing
 * {@link org.codelibs.fess.crawler.exception.CrawlerSystemException} in case of errors.
 * </p>
 *
 * <p>
 * The {@link #storeData(ResponseData, ResultData)} method is the main entry point for storing

                    }
                }
            }

            return readings;
        }
    }

    /**
     * Test implementation that throws exceptions
     */
    private static class TestReadingConverterWithException implements ReadingConverter {

        private boolean throwExceptionOnInit = false;
        private boolean throwExceptionOnConvert = false;

        value = props.getProperty("jcifs.smb.client.nativeLanMan");
        if (value != null) {
            this.nativeLanMan = value;
        }

        // Dialect version properties - these should throw exceptions for invalid values
        String minVersion = props.getProperty("jcifs.smb.client.minVersion");
        String maxVersion = props.getProperty("jcifs.smb.client.maxVersion");

    public static void afterClass() throws Exception {
        runner.close();
        runner.clean();
    }

    @Before
    public void before() throws Exception {
        // Delete test indices and settings indices for complete cleanup
        try {
            runner.admin().indices().prepareDelete("SuggesterRefactoringTest*", "fess_suggest*").execute().actionGet();
        } catch (Exception e) {

おそらくコードの中で直接使用する必要はないでしょう。

しかし、高度なシナリオのために必要な場合には、カスタムヘッダーを追加することができます:

{* ../../docs_src/handling_errors/tutorial002.py hl[14] *}

## カスタム例外ハンドラのインストール

カスタム例外ハンドラは<a href="https://www.starlette.dev/exceptions/" class="external-link" target="_blank">Starletteと同じ例外ユーティリティ</a>を使用して追加することができます。

あなた（または使用しているライブラリ）が`raise`するかもしれないカスタム例外`UnicornException`があるとしましょう。

そして、この例外をFastAPIでグローバルに処理したいと思います。