assertThat(serverSocket.isClosed()).isTrue();
  }

  @SuppressWarnings("Java8ApiChecker")
  static class MyServerExampleWithCleaner implements AutoCloseable {
    private static final Cleaner cleaner = Cleaner.create();

    private static Runnable closeServerSocketRunnable(
        ServerSocket serverSocket, AtomicBoolean cleanerRan) {
      return () -> {
        try {
          serverSocket.close();

/// tip

Additionally, a background task is normally an independent set of logic that should be handled separately, with its own resources (e.g. its own database connection).

So, this way you will probably have cleaner code.

///

But for the generated client, we could **modify** the OpenAPI operation IDs right before generating the clients, just to make those method names nicer and **cleaner**.

We could download the OpenAPI JSON to a file `openapi.json` and then we could **remove that prefixed tag** with a script like this:

{* ../../docs_src/generate_clients/tutorial004_py39.py *}

//// tab | Node.js

     * spot before warnings would be emitted.
     * <p>
     * The method returns a "cleaner" runnable, as during extension loading the context needs to be "cleaned", restored
     * to previous state (as it was before extension loading).
     */
    protected Runnable settings(C context, boolean emitSettingsWarnings, SettingsBuilder settingsBuilder)

                  // is undefined in shutdown hooks.
                  // This is because the logging code installs a shutdown hook of its
                  // own. See Cleaner class inside {@link LogManager}.
                  service.awaitTermination(terminationTimeout, timeUnit);
                } catch (InterruptedException ignored) {
                  // We're shutting down anyway, so just ignore.

                        cleaned++;
                    } catch (Exception e) {
                        log.error("Failed to auto-close resource: {}", holder.resourceId, e);
                    }
                }
            }
        }

        if (cleaned > 0) {
            log.info("Cleaned up {} abandoned resources", cleaned);
        }
    }

    /**

name: Cleanup stale performance test data

on:
  schedule:
    - cron: '0 4 * * 1'  # Run every Monday at 4:00 AM UTC
  workflow_dispatch:

permissions:
  contents: read
  id-token: write

jobs:
  cleanup-stale-performance-data:
    runs-on: ubuntu-latest

    if: github.repository == 'gradle/gradle'

    steps:
      - name: Checkout repository
        uses: actions/checkout@v6
      

                    pathToLease.remove(entry.getValue().getPath());
                    cleaned++;
                    log.debug("Cleaned up expired lease: {}", entry.getKey());
                }
            }

            if (cleaned > 0) {
                log.info("Cleaned up {} expired leases", cleaned);
            }

            return cleaned;
        } finally {
            lock.writeLock().unlock();
        }
    }

- The helping message of commands which have sub-commands is now clearer and more instructive. It will show the full command instead of `kubectl <command> --help ...`
  

        resourceManager.registerResource(resource2);

        assertFalse(resource1.isClosed());
        assertFalse(resource2.isClosed());

        int cleaned = resourceManager.forceCleanup();
        assertTrue(cleaned >= 2);

        assertTrue(resource1.isClosed());
        assertTrue(resource2.isClosed());
    }

    @Test
    @DisplayName("Test leak detection for unclosed resources")