</p>

<h2 id="Blocks">Blocks</h2>

<p>
A <i>block</i> is a possibly empty sequence of declarations and statements
within matching brace brackets.
</p>

<pre class="ebnf">
Block = "{" StatementList "}" .
StatementList = { Statement ";" } .
</pre>

<p>
In addition to explicit blocks in the source code, there are implicit blocks:
</p>

<ol>

pkg syscall (netbsd-arm64), const LOCK_EX = 2
pkg syscall (netbsd-arm64), const LOCK_EX ideal-int
pkg syscall (netbsd-arm64), const LOCK_NB = 4
pkg syscall (netbsd-arm64), const LOCK_NB ideal-int
pkg syscall (netbsd-arm64), const LOCK_SH = 1
pkg syscall (netbsd-arm64), const LOCK_SH ideal-int
pkg syscall (netbsd-arm64), const LOCK_UN = 8
pkg syscall (netbsd-arm64), const LOCK_UN ideal-int

pkg syscall (darwin-arm64), const LOCK_EX = 2
pkg syscall (darwin-arm64), const LOCK_EX ideal-int
pkg syscall (darwin-arm64), const LOCK_NB = 4
pkg syscall (darwin-arm64), const LOCK_NB ideal-int
pkg syscall (darwin-arm64), const LOCK_SH = 1
pkg syscall (darwin-arm64), const LOCK_SH ideal-int
pkg syscall (darwin-arm64), const LOCK_UN = 8
pkg syscall (darwin-arm64), const LOCK_UN ideal-int

// until the action is complete, unless the container process fails, in which case the handler is aborted.
message Lifecycle {
  // PostStart is called immediately after a container is created. If the handler fails,
  // the container is terminated and restarted according to its restart policy.
  // Other management of the container blocks until the hook completes.

); public RuleChain around(TestRule); public org.junit.runners.model.Statement apply(org.junit.runners.model.Statement, org.junit.runner.Description); static void <clinit>(); } org/junit/rules/Stopwatch$Clock.class package org.junit.rules; synchronized class Stopwatch$Clock { void Stopwatch$Clock(); public long nanoTime(); } org/junit/rules/DisableOnDebug.class package org.junit.rules; public synchronized class DisableOnDebug implements TestRule { private final TestRule rule; private final boolean...

- [`KT-53460`](https://youtrack.jetbrains.com/issue/KT-53460) False positive smartcast warning in if block after if block
- [`KT-40851`](https://youtrack.jetbrains.com/issue/KT-40851) False MUST_BE_INITIALIZED_OR_BE_ABSTRACT error for a property which is initialised in the init block
- [`KT-59695`](https://youtrack.jetbrains.com/issue/KT-59695) K2: false negative NON_PUBLIC_CALL_FROM_PUBLIC_INLINE

- For raw block CSI volumes on Kubernetes, kubelet was incorrectly calling CSI NodeStageVolume for every single "map" (i.e. raw block "mount") operation for a volume already attached to the node. This PR ensures it is only called once per volume per node. ([#112403](https://github.com/kubernetes/kubernetes/pull/112403), ...

### OpenStack

In this cycle, SIG OpenStack focused on configuration simplification through smarter defaults and the use of auto-detection wherever feasible (Block Storage API versions, Security Groups) as well as updating API support, including:

*   Block Storage (Cinder) V3 is now supported.
*   Load Balancer (Octavia) V2 is now supported, in addition to Neutron LBaaS V2.
*   Neutron LBaas V1 support has been removed.

enforce limits, it only monitors consumption. To utilize this functionality, set the feature gate `LocalStorageCapacityIsolationFSQuotaMonitoring=true`. For ext4fs filesystems, create the filesystem with `mkfs.ext4 -O project <block_device>` and run `tune2fs -Q prjquota `block device`; XFS filesystems need no additional preparation. The filesystem must be mounted with option `project` in `/etc/fstab`. If the primary partition is the root filesystem, add `rootflags=pquota` to the GRUB config file. ...

* The Local Volume Plugin has been updated to support Block volumeMode PVs. With this change, it is now possible to create local volume PVs for raw block devices. ([#59303](https://github.com/kubernetes/kubernetes/pull/59303), [@dhirajh](https://github.com/dhirajh))