}
	if len(gcsObjects) > 0 {
		return true, nil
	}
	return false, nil
}

func newWarmBackendGCS(conf madmin.TierGCS, tier string) (*warmBackendGCS, error) {
	// Validation code
	if conf.Creds == "" {
		return nil, errors.New("empty credentials unsupported")
	}

	if conf.Bucket == "" {
		return nil, errors.New("no bucket name was provided")
	}

### 5.1 Lease Break Notification
```java
package jcifs.internal.smb2.lease;

import jcifs.internal.smb2.ServerMessageBlock2;

public class Smb2LeaseBreakNotification extends ServerMessageBlock2 {
    // Command code for lease break
    public static final int SMB2_OPLOCK_BREAK = 0x0012;
    
    private int structureSize;
    private int flags;
    private Smb2LeaseKey leaseKey;
    private int currentLeaseState;

    for (int i = 0; i < elements.length; i++) {
      multimap.put(elements[i], i);
    }
  }

  /**
   * Implements {@code Multimap.put()} -- and no other methods -- for a {@code Map} by ignoring all
   * but the latest value for each key. This class exists only so that we can use {@link
   * MultimapsCollectionTest#populateMultimapForGet(Multimap, String[])} and similar methods to

  private static File root() {
    return File.listRoots()[0];
  }

  /** Returns a {@code File} object for the given path parts. */
  private static File file(String first, String... more) {
    return file(new File(first), more);
  }

  /** Returns a {@code File} object for the given path parts. */
  private static File file(File first, String... more) {

「**オペレーションズ**」とも呼ぶことにします。

#### *パスオペレーションデコレータ*を定義

{* ../../docs_src/first_steps/tutorial001.py hl[6] *}
`@app.get("/")`は直下の関数が下記のリクエストの処理を担当することを**FastAPI**に伝えます:

* パス `/`
* <abbr title="an HTTP GET method"><code>get</code> オペレーション</abbr>

/// info | `@decorator` について

Pythonにおける`@something`シンタックスはデコレータと呼ばれます。

「デコレータ」は関数の上に置きます。かわいらしい装飾的な帽子のようです（この用語の由来はそこにあると思います）。

「デコレータ」は直下の関数を受け取り、それを使って何かを行います。

        this.config = config;
    }

    /**
     * Constructor for SMB2 message block with configuration and command.
     *
     * @param config the configuration object
     * @param command the SMB2 command code
     */
    protected ServerMessageBlock2(final Configuration config, final int command) {
        this.config = config;
        this.command = command;
    }

    /**

viewed by doing a GET/HEAD on the object version - it will return a `X-Minio-Replication-DeleteMarker-Status` header and http response code of `405`. In the case of permanent deletes, if the delete replication is pending or failed to propagate to the target cluster, GET/HEAD will return additional `X-Minio-Replication-Delete-Status` header and a http response code of `405`.

![delete](https://raw.githubusercontent.com/minio/minio/master/docs/bucket/replication/DELETE_bucket_replication.png)...

     *
     * @param cfg the configuration to use
     * @param name the NetBIOS name (will be truncated to 15 characters if longer)
     * @param hexCode the NetBIOS name type code
     * @param scope the NetBIOS scope identifier
     */
    public Name(final Configuration cfg, String name, final int hexCode, final String scope) {
        this.config = cfg;
        if (name.length() > 15) {

    /**
     * Tricky case: flat directory structure, but child directory != artifactId.
     * Model interpolation does not give same result when calculated from build or from repo...
     * This is why MNG-5000 fix in code is marked as bad practice (uses file names)
     * @throws IOException Model read problem
     */
    @Test
    void testFlatTrickyUrls() throws IOException {

You can use <a href="https://github.com/pydantic/bump-pydantic" class="external-link" target="_blank">`bump-pydantic`</a> from the same Pydantic team.

This tool will help you to automatically change most of the code that needs to be changed.

After this, you can run the tests and check if everything works. If it does, you are done. 😎

## Pydantic v1 in v2 { #pydantic-v1-in-v2 }