if (logger.isDebugEnabled()) {
                        logger.debug("Failed to change password - user not found: username={}", username);
                    }
                    throw new FessUserNotFoundException(username);
                });
            } else {
                logger.warn("Password change not applied by authentication manager: username={}", username);
            }

of API design and review. Any code should come after this.

[APIs]: https://en.wikipedia.org/wiki/API
[issue]: https://github.com/google/guava/issues

Pull requests
-------------

Unless the change is a trivial fix such as for a typo, it's generally best to
start by opening a new issue describing the bug or feature you're intending to
fix. Even if you think it's relatively minor, it's helpful to know what people

     * Returns the time when the user's password was last changed.
     * @return the password last change timestamp
     */
    public Date getPwdLastChangeTime() {
        return this.pwdLastChangeTime;
    }

    /**
     * Returns the earliest time when the user can change their password.
     * @return the password can change timestamp
     */
    public Date getPwdCanChangeTime() {
        return this.pwdCanChangeTime;

extraVolumeMounts: []

## Additional sidecar containers
extraContainers: []

## Internal port number for MinIO S3 API container
## Change service.port to change external port number
minioAPIPort: "9000"

## Internal port number for MinIO Browser Console container
## Change consoleService.port to change external port number
minioConsolePort: "9001"

## Update strategy for Deployments
deploymentUpdate:
  type: RollingUpdate

export ACCESS_KEY="$2"
export SECRET_KEY="$3"
export JOB_NAME="$4"
export MINT_MODE="full"

docker system prune -f || true
docker volume prune -f || true
docker volume rm $(docker volume ls -f dangling=true) || true

## change working directory
cd .github/workflows/mint

## always pull latest
docker pull docker.io/minio/mint:edge

docker-compose -f minio-${MODE}.yaml up -d
sleep 1m

docker system prune -f || true

{* ../../docs_src/configure_swagger_ui/tutorial001_py39.py hl[3] *}

…и после этого Swagger UI больше не будет показывать подсветку синтаксиса:

<img src="/img/tutorial/extending-openapi/image03.png">

## Изменить тему { #change-the-theme }

Аналогично вы можете задать тему подсветки синтаксиса с ключом "syntaxHighlight.theme" (обратите внимание, что посередине стоит точка):

{* ../../docs_src/configure_swagger_ui/tutorial002_py39.py hl[3] *}

import jcifs.internal.smb1.trans.nt.FileNotifyInformationImpl;
import jcifs.internal.smb2.ServerMessageBlock2Response;
import jcifs.internal.util.SMBUtil;
import jcifs.smb.NtStatus;

/**
 * SMB2 Change Notify response message.
 *
 * This response contains information about file system changes
 * that occurred in the monitored directory.
 *
 * @author mbechler
 */

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

### Ellipsis

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

{* ../../docs_src/configure_swagger_ui/tutorial001_py39.py hl[3] *}

...y entonces Swagger UI ya no mostrará el resaltado de sintaxis:

<img src="/img/tutorial/extending-openapi/image03.png">

## Cambiar el tema { #change-the-theme }

De la misma manera, podrías configurar el tema del resaltado de sintaxis con la clave `"syntaxHighlight.theme"` (ten en cuenta que tiene un punto en el medio):

aspects of a component while ignoring others.

These stubs form an internally consistent data-set that is not expected to change. They are
used to test the individual components in the lifecycle with data that has expected characteristics
and can be asserted as desired.

You can change/extend these stubs, and tests should not be breaking too much, since most tests