assertThat(rewrittenResponse.trailers()).isEqualTo(headersOf("t1", "v1"))
    }
  }

  /**
   * We had a bug where a custom `ResponseBody` interacted poorly with `Response.trailers()`.
   * Confirm custom trailers can be read without even accessing the response body.
   */
  @Test
  fun customTrailersDoNotUseResponseBody() {
    val response =
      Response

                log.debug("  Excluded {}", id);
            } else {
                Path file = artifact.getPath();
                log.debug("  Included {} located at {}", id, file);
                realm.addURL(file.toUri().toURL());
            }
        }
        return CoreExtensionEntry.discoverFrom(
                realm,
                Collections.singleton(artifacts.get(0).getPath().toFile()),

   * element). Note that for an {@link Object#equals}-based multiset, this gives the same result as
   * {@link Collections#frequency} (which would presumably perform more poorly).
   *
   * <p><b>Note:</b> the utility method {@link Iterables#frequency} generalizes this operation; it
   * correctly delegates to this method when dealing with a multiset, but it can also accept any

name: 'Close stale PRs'
on:
  schedule:
    # Execute every hour at xx:05 to avoid conflicts with other workflows
    - cron: '5 * * * *'

permissions: {}

jobs:
  stale:
    permissions:
      pull-requests: write

    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v10
        with:
          operations-per-run: 50
          ascending: true
          exempt-all-milestones: true

    private ScheduledFuture<?> cleanupTask;
    private volatile boolean shutdownInProgress = false;

    // Configuration
    private long maxResourceAge = TimeUnit.HOURS.toMillis(1); // 1 hour default
    private long cleanupInterval = TimeUnit.MINUTES.toMillis(5); // 5 minutes default
    private boolean leakDetectionEnabled = true;
    private boolean autoCleanupEnabled = true;

    /**

        «««
        ## Typhinweise und –annotationen { #type-hints-and-annotations }
        »»»

3.2) Do not apply rule 3 to the untranslated part of the heading inside curly brackets, which you shall not translate.


### German instructions, when to use and when not to use hyphens in words (written in first person, which is you)

# Concurrency and async / await { #concurrency-and-async-await }

Details about the `async def` syntax for *path operation functions* and some background about asynchronous code, concurrency, and parallelism.

## In a hurry? { #in-a-hurry }

<abbr title="too long; didn't read"><strong>TL;DR:</strong></abbr>

If you are using third party libraries that tell you to call them with `await`, like:

```Python
results = await some_library()
```

	"github.com/minio/minio/internal/config"
	"github.com/minio/minio/internal/crypto"
	"github.com/minio/pkg/v3/ldap"
)

const (
	defaultLDAPExpiry = time.Hour * 1

	minLDAPExpiry time.Duration = 15 * time.Minute
	maxLDAPExpiry time.Duration = 365 * 24 * time.Hour
)

// Config contains AD/LDAP server connectivity information.
type Config struct {
	LDAP ldap.Config

You could also define it as a normal function instead of `async def`:

{* ../../docs_src/first_steps/tutorial003_py39.py hl[7] *}

/// note

If you don't know the difference, check the [Async: *"In a hurry?"*](../async.md#in-a-hurry){.internal-link target=_blank}.

///

### Step 5: return the content { #step-5-return-the-content }

{* ../../docs_src/first_steps/tutorial001_py39.py hl[8] *}

# Конкурентность и async / await { #concurrency-and-async-await }

Подробности о синтаксисе `async def` для *функций-обработчиков пути* и немного фона об асинхронном коде, конкурентности и параллелизме.

## Нет времени? { #in-a-hurry }

<abbr title="too long; didn't read – слишком длинно; не читал"><strong>TL;DR:</strong></abbr>

Если вы используете сторонние библиотеки, которые нужно вызывать с `await`, например:

```Python
results = await some_library()