}
            break;
        default:
            break;
        }
        return OptionalEntity.empty();
    }

    /**
     * Get the bad word.
     * @param form The create form.
     * @return The bad word.
     */
    public static OptionalEntity<BadWord> getBadWord(final CreateForm form) {
        final SystemHelper systemHelper = ComponentUtil.getSystemHelper();

      int result = BigIntegerMath.log2(x, HALF_UP);
      BigInteger x2 = x.pow(2);
      // x^2 < 2^(2 * result + 1), or else we would have rounded up
      assertTrue(ZERO.setBit(2 * result + 1).compareTo(x2) > 0);
      // x^2 >= 2^(2 * result - 1), or else we would have rounded down
      assertTrue(result == 0 || ZERO.setBit(2 * result - 1).compareTo(x2) <= 0);
    }
  }

  public void testLog2HalfDown() {

 *       continuing to run {@code FooTest} itself. This is exactly what happens with {@code
 *       AndroidIncompatible}. But I'm not sure what would happen if we annotated the {@code
 *       suite()} method with {@code Suppress}. Would {@code FooTest} itself be suppressed, too?
 *   <li>In at least one case, a use of {@code sun.misc.FpUtils}, the test will not even

      description: "Is the goal of this change a performance improvement? If so, what quantifiable improvement should we expect? How would we measure it?"
    validations:
      required: false

  - type: textarea
    id: learning-curve
    attributes:
      label: "Would this change make Go easier or harder to learn, and why?"

  - type: textarea
    id: cost-description
    attributes:

```
.
├── app
│   ├── __init__.py
│   ├── main.py
│   └── test_main.py
```

The file `main.py` would have:

{* ../../docs_src/async_tests/main.py *}

The file `test_main.py` would have the tests for `main.py`, it could look like this now:

{* ../../docs_src/async_tests/test_main.py *}

## Run it { #run-it }

You can run your tests as usual via:

### High availability

A stand-alone MinIO server would go down if the server hosting the drives goes offline. In contrast, a distributed MinIO setup with _m_ servers and _n_ drives will have your data safe as long as _m/2_ servers or _m*n_/2 or more drives are online.

 * <li>{@link #addBadWord(String, boolean)} - Add a bad word and optionally apply it.
 * <li>{@link #deleteBadWord(String)} - Delete a bad word.
 * <li>{@link #addElevateWord(ElevateWord, boolean)} - Add an elevate word and optionally apply it.
 * <li>{@link #deleteElevateWord(String, boolean)} - Delete an elevate word and optionally apply it.

package org.codelibs.fess.app.web.api.admin.elevateword;

import org.codelibs.fess.app.web.admin.elevateword.DownloadForm;

/**
 * Download body for elevate word API operations.
 * This class extends the DownloadForm to provide request body handling
 * for downloading elevate word configurations via REST API.
 *
 */
public class DownloadBody extends DownloadForm {

    /**
     * Default constructor.
     */

 */
package org.codelibs.fess.app.web.api.admin.badword;

import org.codelibs.fess.app.web.admin.badword.DownloadForm;

/**
 * Download body for Bad Word API operations.
 * This class extends the DownloadForm to provide request body handling
 * for downloading bad word dictionaries via REST API.
 *
 */
public class DownloadBody extends DownloadForm {

    /**
     * Default constructor.
     */

package org.codelibs.fess.app.web.api.admin.badword;

import org.codelibs.fess.app.web.admin.badword.EditForm;

/**
 * Request body class for bad word edit operations in the admin REST API.
 * This class extends EditForm to inherit the necessary form validation and binding capabilities
 * for bad word management operations.
 */
public class EditBody extends EditForm {

    /**
     * Default constructor.
     */
    public EditBody() {