pkg syscall (darwin-arm64), type Rusage struct, Msgrcv int64
pkg syscall (darwin-arm64), type Rusage struct, Msgsnd int64
pkg syscall (darwin-arm64), type Rusage struct, Nivcsw int64
pkg syscall (darwin-arm64), type Rusage struct, Nsignals int64
pkg syscall (darwin-arm64), type Rusage struct, Nswap int64
pkg syscall (darwin-arm64), type Rusage struct, Nvcsw int64
pkg syscall (darwin-arm64), type Rusage struct, Oublock int64

pkg syscall (netbsd-arm64-cgo), type Rusage struct, Msgrcv int64
pkg syscall (netbsd-arm64-cgo), type Rusage struct, Msgsnd int64
pkg syscall (netbsd-arm64-cgo), type Rusage struct, Nivcsw int64
pkg syscall (netbsd-arm64-cgo), type Rusage struct, Nsignals int64
pkg syscall (netbsd-arm64-cgo), type Rusage struct, Nswap int64
pkg syscall (netbsd-arm64-cgo), type Rusage struct, Nvcsw int64
pkg syscall (netbsd-arm64-cgo), type Rusage struct, Oublock int64

- Graduated the following kubelet resource metrics to **general availability**:
  - `container_cpu_usage_seconds_total`
  - `container_memory_working_set_bytes`
  - `container_start_time_seconds`
  - `node_cpu_usage_seconds_total`
  - `node_memory_working_set_bytes`
  - `pod_cpu_usage_seconds_total`
  - `pod_memory_working_set_bytes`
  - `resource_scrape_error`
  

// ---
// New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
//  1. Ignored fields.  It includes many fields which are not generally honored.  For instance, ResourceVersion and FieldPath are both very rarely valid in actual usage.
//  2. Invalid usage help.  It is impossible to add specific help for individual usage.  In most embedded usages, there are particular

- [`KT-53971`](https://youtrack.jetbrains.com/issue/KT-53971) Partial linkage: turning inner class into nested: without usage in executable Native is successful, JavaScript fails
- [`KT-53972`](https://youtrack.jetbrains.com/issue/KT-53972) Partial linkage: turning inner class into nested: with usage in executable Native fails with NPE in backend

- In the kubelet resource metrics endpoint at /metrics/resource, change the names of the following metrics:
  - node_cpu_usage_seconds --> node_cpu_usage_seconds_total
  - container_cpu_usage_seconds --> container_cpu_usage_seconds_total

- Fixes an issue calculating total CPU usage reported for Windows nodes ([#122999](https://github.com/kubernetes/kubernetes/pull/122999), [@marosset](https://github.com/marosset)) [SIG Node and Windows]

### Other (Cleanup or Flake)

- Following metrics from kubelet are now marked as with the ALPHA stability level:
  `node_cpu_usage_seconds_total`
  `node_memory_working_set_bytes`
  `container_cpu_usage_seconds_total`
  `container_memory_working_set_bytes`
  `scrape_error`
  ([#84987](https://github.com/kubernetes/kubernetes/pull/84987), [@RainbowMango](https://github.com/RainbowMango))

    * The vSphere cloud provider has a cleanup function with a loop,
    * inside of which a write lock was intended to prevent races against
    * VM creation, but the usage of the sync.RWMutex type is incorrect,
    * plus is placed in a defer call so the locking is effectively
    * nonexistent.  This patch adds an anonymous function call inside