,"returnFalse","expectSync","err","safeActiveElement","on","types","one","origFn","event","off","leverageNative","notAsync","saved","isTrigger","delegateType","stopPropagation","stopImmediatePropagation","preventDefault","trigger","Event","handleObjIn","eventHandle","events","t","handleObj","handlers","namespaces","origType","elemData","create","handle","triggered","dispatch","bindType","delegateCount","setup","mappedTypes","origCount","teardown","removeEvent","nativeEvent","handlerQueue","fix",...

pkg syscall (darwin-arm64), const NOTE_TRACKERR = 2
pkg syscall (darwin-arm64), const NOTE_TRACKERR ideal-int
pkg syscall (darwin-arm64), const NOTE_TRIGGER = 16777216
pkg syscall (darwin-arm64), const NOTE_TRIGGER ideal-int
pkg syscall (darwin-arm64), const NOTE_USECONDS = 2
pkg syscall (darwin-arm64), const NOTE_USECONDS ideal-int
pkg syscall (darwin-arm64), const NOTE_VM_ERROR = 268435456

build:nonccl --define=no_nccl_support=true

# Modular TF build options
build:dynamic_kernels --define=dynamic_loaded_kernels=true
build:dynamic_kernels --copt=-DAUTOLOAD_DYNAMIC_KERNELS

# Don't trigger --config=<host platform> when cross-compiling.
build:android --noenable_platform_specific_config
build:ios --noenable_platform_specific_config

# Suppress all C++ compiler warnings, otherwise build logs become 10s of MBs.

pkg syscall (freebsd-arm64), const NOTE_TRACKERR = 2
pkg syscall (freebsd-arm64), const NOTE_TRACKERR ideal-int
pkg syscall (freebsd-arm64), const NOTE_TRIGGER = 16777216
pkg syscall (freebsd-arm64), const NOTE_TRIGGER ideal-int
pkg syscall (freebsd-arm64), const NOTE_WRITE = 2
pkg syscall (freebsd-arm64), const NOTE_WRITE ideal-int
pkg syscall (freebsd-arm64), const O_ACCMODE = 3

- Ensure Job status updates are batched by 1s. This fixes an unlikely scenario when a sequence of immediately 
  completing pods could trigger a sequence of non-batched Job status updates. ([#118470](https://github.com/kubernetes/kubernetes/pull/118470), [@mimowo](https://github.com/mimowo)) [SIG Apps]

* flexvolume: trigger plugin init only for the relevant plugin while probe ([#58519](https://github.com/kubernetes/kubernetes/pull/58519), [@linyouchong](https://github.com/linyouchong))

```Python hl_lines="1  3" title="app/routers/users.py"
{!../../../docs_src/bigger_applications/app/routers/users.py!}
```

### *➡ 🛠️* ⏮️ `APIRouter`

& ⤴️ 👆 ⚙️ ⚫️ 📣 👆 *➡ 🛠️*.

⚙️ ⚫️ 🎏 🌌 👆 🔜 ⚙️ `FastAPI` 🎓:

```Python hl_lines="6  11  16" title="app/routers/users.py"
{!../../../docs_src/bigger_applications/app/routers/users.py!}
```

👆 💪 💭 `APIRouter` "🐩 `FastAPI`" 🎓.

```Python hl_lines="1  3" title="app/routers/users.py"
{!../../../docs_src/bigger_applications/app/routers/users.py!}
```

### *Path operations* with `APIRouter`

And then you use it to declare your *path operations*.

Use it the same way you would use the `FastAPI` class:

```Python hl_lines="6  11  16" title="app/routers/users.py"
{!../../../docs_src/bigger_applications/app/routers/users.py!}
```

- Fixed a bug where a change in the `appProtocol` for a Service did not trigger a load balancer update. ([#113033](https://github.com/kubernetes/kubernetes/pull/113033), [@MartinForReal](https://github.com/MartinForReal)) [SIG Cloud Provider and Network]

你可以导入它并通过与 `FastAPI` 类相同的方式创建一个「实例」：

```Python hl_lines="1  3" title="app/routers/users.py"
{!../../../docs_src/bigger_applications/app/routers/users.py!}
```

### 使用 `APIRouter` 的*路径操作*

然后你可以使用它来声明*路径操作*。

使用方式与 `FastAPI` 类相同：

```Python hl_lines="6  11  16" title="app/routers/users.py"
{!../../../docs_src/bigger_applications/app/routers/users.py!}
```

你可以将 `APIRouter` 视为一个「迷你 `FastAPI`」类。

所有相同的选项都得到支持。