pkg debug/elf, const R_386_PC16 R_386
pkg debug/elf, const R_386_PC8 = 23
pkg debug/elf, const R_386_PC8 R_386
pkg debug/elf, const R_386_SIZE32 = 38
pkg debug/elf, const R_386_SIZE32 R_386
pkg debug/elf, const R_386_TLS_DESC = 41
pkg debug/elf, const R_386_TLS_DESC R_386
pkg debug/elf, const R_386_TLS_DESC_CALL = 40
pkg debug/elf, const R_386_TLS_DESC_CALL R_386
pkg debug/elf, const R_386_TLS_GOTDESC = 39
pkg debug/elf, const R_386_TLS_GOTDESC R_386

	_ = x[ErrNoSuchLifecycleConfiguration-37]
	_ = x[ErrInvalidLifecycleWithObjectLock-38]
	_ = x[ErrNoSuchBucketSSEConfig-39]
	_ = x[ErrNoSuchCORSConfiguration-40]
	_ = x[ErrNoSuchWebsiteConfiguration-41]
	_ = x[ErrReplicationConfigurationNotFoundError-42]
	_ = x[ErrRemoteDestinationNotFoundError-43]
	_ = x[ErrReplicationDestinationMissingLock-44]
	_ = x[ErrRemoteTargetNotFoundError-45]

---

### Phase 4: Directory Leasing
**Priority: MEDIUM** | **Estimated Effort: 2-3 weeks**

Directory leasing extends the lease concept to directories for improved metadata caching.

#### 4.1 Core Directory Lease Infrastructure
```
Package: jcifs.internal.smb2.lease
├── DirectoryLeaseContext.java    - Directory-specific lease context
├── DirectoryLeaseCache.java      - Directory metadata cache

OkHttp 3.x Change Log
=====================

## Version 3.14.9

_2020-05-17_

 *  Fix: Don't crash when running as a plugin in Android Studio Canary 4.1. To enable
    platform-specific TLS features OkHttp must detect whether it's running in a JVM or in Android.
    The upcoming Android Studio runs in a JVM but has classes from Android and that confused OkHttp!


## Version 3.14.8

_2020-04-28_

    RECURSIVE_TREE,        // Entire subtree (if supported)
    METADATA_ONLY,         // File attributes but not content
    FULL_ENUMERATION      // Complete directory listing
}
```

## 4. Data Structures

### 4.1 Directory Lease Context
```java
package jcifs.internal.smb2.lease;

public class DirectoryLeaseContext extends Smb2LeaseContext {
    public static final String NAME_DIRECTORY_REQUEST = "DLse";

     */
    void shutdown();
}

public enum RdmaAccess {
    LOCAL_READ,
    LOCAL_WRITE,
    REMOTE_READ,
    REMOTE_WRITE,
    MEMORY_BIND
}
```

## 4. Data Structures

### 4.1 RDMA Connection
```java
package jcifs.internal.smb2.rdma;

import java.nio.ByteBuffer;
import java.util.concurrent.BlockingQueue;
import java.util.concurrent.LinkedBlockingQueue;

        assertTrue(restriction.isUpperBoundInclusive(), CHECK_UPPER_BOUND_INCLUSIVE);

        range1 = VersionRange.createFromVersionSpec("[1.0,1.2],[1.3,1.7]");
        range2 = VersionRange.createFromVersionSpec("[1.1,1.4],[1.5,1.6]");
        mergedRange = range1.restrict(range2);
        assertNull(mergedRange.getRecommendedVersion(), CHECK_VERSION_RECOMMENDATION);
        restrictions = mergedRange.getRestrictions();

///

## 複数のモデル

ここでは、パスワードフィールドをもつモデルがどのように見えるのか、また、どこで使われるのか、大まかなイメージを紹介します:

{* ../../docs_src/extra_models/tutorial001.py hl[9,11,16,22,24,29:30,33:35,40:41] *}

### `**user_in.dict()`について

#### Pydanticの`.dict()`

`user_in`は`UserIn`クラスのPydanticモデルです。

Pydanticモデルには、モデルのデータを含む`dict`を返す`.dict()`メソッドがあります。

そこで、以下のようなPydanticオブジェクト`user_in`を作成すると:

  static final String E13 = "1-3";
  static final String E14 = "1-4";
  static final String E23 = "2-3";
  static final String E31 = "3-1";
  static final String E34 = "3-4";
  static final String E41 = "4-1";
  static final String E15 = "1-5";
  static final String EDGE_NOT_IN_GRAPH = "edgeNotInGraph";

  // TODO(user): Consider separating Strings that we've defined here to capture

}
```

### 3.2 Lease Versions
- **Lease V1**: Basic lease support (SMB 3.0)
- **Lease V2**: Adds epoch support for better consistency (SMB 3.0.2+)

## 4. Data Structures

### 4.1 Lease Key Structure
```java
package jcifs.internal.smb2.lease;

import java.security.SecureRandom;
import java.util.Arrays;

public class Smb2LeaseKey {
    private final byte[] key;  // 16-byte lease key