Szymon Habrainski

feat(core,common,testing): support overriding middleware for testing

2

closes: #4073 ## PR Checklist Please check if your PR fulfills the following requirements: - [x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md - [x] Tests for the changes have...

## PR Checklist Please check if your PR fulfills the following requirements: - [x] The commit message follows our guidelines: https://github.com/nestjs/docs.nestjs.com/blob/master/CONTRIBUTING.md ## PR Type What kind of change does this...

Repetitive ```IndexOutOfBoundsException```s

5

Under "IDE Fatal Errors" I repeatedly get following error: ### stacktrace.txt ``` java.lang.IndexOutOfBoundsException: Wrong offset: 6293. Should be in range: [0, 6268] at com.intellij.openapi.editor.impl.LineSet.findLineIndex(LineSet.java:166) at com.intellij.openapi.editor.impl.DocumentImpl.getLineNumber(DocumentImpl.java:1005) at com.daniel_espinoza.inline_error.InlineErrorAction.$anonfun$highlightError$2(InlineErrorAction.scala:60) at scala.collection.immutable.List.map(List.scala:246)...

> [!NOTE] > This PR is still a draft. This PR implements batch replication as described in #40. TODO: PR description.

feat: support request hedging

1

> [!NOTE] > This PR is still a draft. This includes this description. # Motivation: This PR enables `RetryingClient` and `RetryingRpcClient` to perform request hedging. ## What is request hedging?...

This issue originates from [a user's question](https://discord.com/channels/1087271586832318494/1384091584076845090/1384111200232538112) on Discord. gRPC enables client-side request/retry throttling via a token-based mechanism: https://github.com/grpc/proposal/blob/master/A6-client-retries.md#throttling-retry-attempts-and-hedged-rpcs. Armeria currently supports throttling only on the server side. This issue...

Add `perMethod`, `perHost`, `perPath` and builder to `RetryConfigMapping`

4

Motivation: The motivation of this PR is explained in the [associated issue](https://github.com/line/armeria/issues/6242#issue-3070603802). Modifications: - Added `perMethod`, `perHost`, `perPath` and `perHostAndMethod` to `RetryConfigMapping` to enable retry configuration on a per method,...

Enable creating a `RetryConfigMapping` on a per method, path, or host basis

1

## Motivation If a user wants to construct a caching `RetryConfigMapping`, they can currently do so by: 1. Subclassing `RetryConfigMapping`, or 2. Using ```java RetryConfigMapping.of( BiFunction

Add verifications of `ClientRequestContext`s to `RetryClientTest` and `RetryingRpcClientTest`

3

## Motivation: `RetryingClientTest` and `RetryingRpcClientTest` validate the respective retrying clients under various (failure) conditions. However, not all test cases check whether the client-side request log is properly propagated by the...

Extract `AbstractRetryingClient.State` into `RetryContext` and `RetryCounter`

6

## Motivation: Currently, `AbstractRetryingClient` manages `ctx.attr(STATE)`, while `Retrying(Rpc)Client` passes a "backpack state" by forwarding multiple parameters through internal methods. This leads to several issues: 1. Backpacking that many parameters makes...