pkg syscall (freebsd-arm64), const AF_CHAOS = 5
pkg syscall (freebsd-arm64), const AF_CHAOS ideal-int
pkg syscall (freebsd-arm64), const AF_CNT = 21
pkg syscall (freebsd-arm64), const AF_CNT ideal-int
pkg syscall (freebsd-arm64), const AF_COIP = 20
pkg syscall (freebsd-arm64), const AF_COIP ideal-int
pkg syscall (freebsd-arm64), const AF_DATAKIT = 9
pkg syscall (freebsd-arm64), const AF_DATAKIT ideal-int

pkg syscall (freebsd-riscv64), const AF_APPLETALK ideal-int #53466
pkg syscall (freebsd-riscv64), const AF_ARP = 35 #53466
pkg syscall (freebsd-riscv64), const AF_ARP ideal-int #53466
pkg syscall (freebsd-riscv64), const AF_ATM = 30 #53466
pkg syscall (freebsd-riscv64), const AF_ATM ideal-int #53466
pkg syscall (freebsd-riscv64), const AF_BLUETOOTH = 36 #53466
pkg syscall (freebsd-riscv64), const AF_BLUETOOTH ideal-int #53466

none;\n  }\n}\n\n.popover-body {\n  padding: var(--#{$prefix}popover-body-padding-y) var(--#{$prefix}popover-body-padding-x);\n  color: var(--#{$prefix}popover-body-color);\n}\n","// Notes on the classes:\n//\n// 1. .carousel.pointer-event should ideally be pan-y (to allow for users to scroll vertically)\n//    even when their scroll action started on a carousel, but for compatibility (with Firefox)\n//    we're preventing all actions instead\n// 2. The .carousel-item-start and .carousel-item-end...

    *   output tensors of one layer is used in the constructor of another.
    *   symbolic tensors outside the scope of the model are used in custom loss
        functions. The flag can be disabled for these cases and ideally the
        usage pattern will need to be fixed.
    *   Mark Keras `set_session` as `compat.v1` only.
    *   `tf.keras.estimator.model_to_estimator` now supports exporting to

r-border-radius);\n\n  &:empty {\n    display: none;\n  }\n}\n\n.popover-body {\n  padding: $popover-body-padding-y $popover-body-padding-x;\n  color: $popover-body-color;\n}\n","// Notes on the classes:\n//\n// 1. .carousel.pointer-event should ideally be pan-y (to allow for users to scroll vertically)\n//    even when their scroll action started on a carousel, but for compatibility (with Firefox)\n//    we're preventing all actions instead\n// 2. The .carousel-item-left and .carousel-item-right...

  - [Known Issues](#known-issues)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)
    - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
  - [Changes by Kind](#changes-by-kind-16)
    - [Deprecation](#deprecation)
    - [API Change](#api-change-4)
    - [Feature](#feature-8)

(R18+Rkeyp), V17 \ LXVD2X (R19+Rkeyp), V18 \ LXVD2X (R20+Rkeyp), V19 \ LXVD2X (R21+Rkeyp), V20 // Perform aes cipher operation for keysize 10/12/14 using the keys // loaded by LOAD_KEY, and key size information held in CR1EQ/CR2EQ. // // Vxor is ideally V6 (Key[0-3]), but for slightly improved encrypting // performance V6 and IVEC can be swapped (xor is both associative and // commutative) during encryption: // // VXOR INOUT, IVEC, INOUT // VXOR INOUT, V6, INOUT // // into // // VXOR INOUT, V6, INOUT...

* 📌 Pin Swagger UI version to 5.9.0 temporarily to handle a bug crashing it in 5.9.1. PR [#10529](https://github.com/tiangolo/fastapi/pull/10529) by [@alejandraklachquin](https://github.com/alejandraklachquin).
    * This is not really a bug in FastAPI but in Swagger UI, nevertheless pinning the version will work while a solution is found on the [Swagger UI side](https://github.com/swagger-api/swagger-ui/issues/9337).

### Docs