pkg syscall (netbsd-arm64-cgo), const PTRACE_CONT = 7
pkg syscall (netbsd-arm64-cgo), const PTRACE_CONT ideal-int
pkg syscall (netbsd-arm64-cgo), const PTRACE_KILL = 8
pkg syscall (netbsd-arm64-cgo), const PTRACE_KILL ideal-int
pkg syscall (netbsd-arm64-cgo), const PTRACE_TRACEME = 0
pkg syscall (netbsd-arm64-cgo), const PTRACE_TRACEME ideal-int

pkg syscall (darwin-arm64), const PROT_WRITE ideal-int
pkg syscall (darwin-arm64), const PTRACE_CONT = 7
pkg syscall (darwin-arm64), const PTRACE_CONT ideal-int
pkg syscall (darwin-arm64), const PTRACE_KILL = 8
pkg syscall (darwin-arm64), const PTRACE_KILL ideal-int
pkg syscall (darwin-arm64), const PTRACE_TRACEME = 0
pkg syscall (darwin-arm64), const PTRACE_TRACEME ideal-int
pkg syscall (darwin-arm64), const PT_ATTACH = 10

* fixes kubefed's ability to create RBAC roles in version-skewed clusters ([#50537](https://github.com/kubernetes/kubernetes/pull/50537), [@liggitt](https://github.com/liggitt))
* Fix data race during addition of new CRD ([#50098](https://github.com/kubernetes/kubernetes/pull/50098), [@nikhita](https://github.com/nikhita))

- The `rules` field in RBAC `Role` and `ClusterRole` objects is now correctly reported as optional in the openapi schema. ([#73250](https://github.com/kubernetes/kubernetes/pull/73250), [@liggitt](https://github.com/liggitt))

 - `kubeadm`: a separate "super-admin.conf" file is now deployed. The User in `admin.conf` is now bound to a new RBAC Group `kubeadm:cluster-admins` that has `cluster-admin` `ClusterRole` access. The User in `super-admin.conf` is now bound to the `system:masters` built-in super-powers / break-glass Group that can bypass RBAC. Before this change, the default `admin.conf` was bound to `system:masters` Group, which was undesired. Executing `kubeadm init phase kubeconfig...

TypeName form of the LiteralType appears as an operand between the
<a href="#Keywords">keyword</a> and the opening brace of the block
of an "if", "for", or "switch" statement, and the composite literal
is not enclosed in parentheses, square brackets, or curly braces.
In this rare case, the opening brace of the literal is erroneously parsed
as the one introducing the block of statements. To resolve the ambiguity,

- cloud.google.com/go/speech: v1.15.0
- cloud.google.com/go/storagetransfer: v1.8.0
- cloud.google.com/go/talent: v1.5.0
- cloud.google.com/go/texttospeech: v1.6.0
- cloud.google.com/go/tpu: v1.5.0
- cloud.google.com/go/trace: v1.9.0
- cloud.google.com/go/translate: v1.7.0
- cloud.google.com/go/video: v1.15.0
- cloud.google.com/go/videointelligence: v1.10.0
- cloud.google.com/go/vision/v2: v2.7.0
- cloud.google.com/go/vmmigration: v1.6.0

#### **RBAC**

*   New permissions have been added to default RBAC roles ([#52654](https://github.com/kubernetes/kubernetes/pull/52654),[ @liggitt](https://github.com/liggitt)):
    *   The default admin and edit roles now include read/write permissions
    *   The view role includes read permissions on poddisruptionbudget.policy resources.

public synchronized class TestFailure { protected Test fFailedTest; protected Throwable fThrownException; public void TestFailure(Test, Throwable); public Test failedTest(); public Throwable thrownException(); public String toString(); public String trace(); public String exceptionMessage(); public boolean isFailure(); } junit/framework/JUnit4TestAdapterCac$1.class package junit.framework; synchronized class JUnit4TestAdapterCac$1 extends org.junit.runner.notification.RunListener { void JUnit4TestA...