Bring the 'jakarta' branch up to date with tag '5.6.0' #731
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [micrometer-core](https://github.com/micrometer-metrics/micrometer) from 1.9.1 to 1.9.2. - [Release notes](https://github.com/micrometer-metrics/micrometer/releases) - [Commits](micrometer-metrics/micrometer@v1.9.1...v1.9.2) --- updated-dependencies: - dependency-name: io.micrometer:micrometer-core dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [pitest-maven](https://github.com/hcoles/pitest) from 1.9.1 to 1.9.2. - [Release notes](https://github.com/hcoles/pitest/releases) - [Commits](hcoles/pitest@1.9.1...1.9.2) --- updated-dependencies: - dependency-name: org.pitest:pitest-maven dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [dokka-maven-plugin](https://github.com/Kotlin/dokka) from 1.7.0 to 1.7.10. - [Release notes](https://github.com/Kotlin/dokka/releases) - [Commits](https://github.com/Kotlin/dokka/commits) --- updated-dependencies: - dependency-name: org.jetbrains.dokka:dokka-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…tbrains.dokka-dokka-maven-plugin-1.7.10 Bump dokka-maven-plugin from 1.7.0 to 1.7.10
…test-pitest-maven-1.9.2 Bump pitest-maven from 1.9.1 to 1.9.2
…rometer-micrometer-core-1.9.2 Bump micrometer-core from 1.9.1 to 1.9.2
Bumps [kotlinx-coroutines-jdk8](https://github.com/Kotlin/kotlinx.coroutines) from 1.6.3 to 1.6.4. - [Release notes](https://github.com/Kotlin/kotlinx.coroutines/releases) - [Changelog](https://github.com/Kotlin/kotlinx.coroutines/blob/master/CHANGES.md) - [Commits](Kotlin/kotlinx.coroutines@1.6.3...1.6.4) --- updated-dependencies: - dependency-name: org.jetbrains.kotlinx:kotlinx-coroutines-jdk8 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…tbrains.kotlinx-kotlinx-coroutines-jdk8-1.6.4 Bump kotlinx-coroutines-jdk8 from 1.6.3 to 1.6.4
Bumps [smallrye-config](https://github.com/smallrye/smallrye-config) from 2.10.1 to 2.11.0. - [Release notes](https://github.com/smallrye/smallrye-config/releases) - [Commits](smallrye/smallrye-config@2.10.1...2.11.0) --- updated-dependencies: - dependency-name: io.smallrye.config:smallrye-config dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…llrye.config-smallrye-config-2.11.0 Bump smallrye-config from 2.10.1 to 2.11.0
Bumps [pitest-maven](https://github.com/hcoles/pitest) from 1.9.2 to 1.9.3. - [Release notes](https://github.com/hcoles/pitest/releases) - [Commits](hcoles/pitest@1.9.2...1.9.3) --- updated-dependencies: - dependency-name: org.pitest:pitest-maven dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…test-pitest-maven-1.9.3 Bump pitest-maven from 1.9.2 to 1.9.3
Add rate limit
…logs Add more information to Retry/Timeout logs
The `Clock` abstraction was introduced to support rate limit, but is in fact unnecessary and can be replaced by the existing `Stopwatch` abstraction. This has an additional advantage: the `SystemStopwatch` implementation uses `System.nanoTime()` and hence is monotonic, while `SystemClock` used `System.currentTimeMillis()` and so was not.
remove the notion of Clock
Fix unnecessary String concatenation in debug/trace statements.
Bumps [maven-resources-plugin](https://github.com/apache/maven-resources-plugin) from 3.2.0 to 3.3.0. - [Release notes](https://github.com/apache/maven-resources-plugin/releases) - [Commits](apache/maven-resources-plugin@maven-resources-plugin-3.2.0...maven-resources-plugin-3.3.0) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-resources-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…ache.maven.plugins-maven-resources-plugin-3.3.0 Bump maven-resources-plugin from 3.2.0 to 3.3.0
Bumps [junit-bom](https://github.com/junit-team/junit5) from 5.8.2 to 5.9.0. - [Release notes](https://github.com/junit-team/junit5/releases) - [Commits](junit-team/junit5@r5.8.2...r5.9.0) --- updated-dependencies: - dependency-name: org.junit:junit-bom dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…nit-junit-bom-5.9.0 Bump junit-bom from 5.8.2 to 5.9.0
This is only enabled in the non-compatible mode, even though the TCK doesn't test this particular declaration scheme. Some other features on top of the specification do not require non-compatible mode, but those always use some SmallRye Fault Tolerance specific API. Also this commit slightly changes how fallback methods are looked up. The previous code looked up fallback methods based on the parameter types and later verified the return type. That allowed a bit more precise error message in case the return types don't match. With this change, the fallback method code checks the return type together with the parameter types, so that all fallback method lookup rules are centralized. The error message in case of mismatching return type is slightly more generic than before, but that's not a big deal.
…eption add support for fallback methods with exception parameter
Bumps [smallrye-config](https://github.com/smallrye/smallrye-config) from 2.11.0 to 2.11.1. - [Release notes](https://github.com/smallrye/smallrye-config/releases) - [Commits](smallrye/smallrye-config@2.11.0...2.11.1) --- updated-dependencies: - dependency-name: io.smallrye.config:smallrye-config dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [micrometer-core](https://github.com/micrometer-metrics/micrometer) from 1.9.2 to 1.9.3. - [Release notes](https://github.com/micrometer-metrics/micrometer/releases) - [Commits](micrometer-metrics/micrometer@v1.9.2...v1.9.3) --- updated-dependencies: - dependency-name: io.micrometer:micrometer-core dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…tx-vertx-core-4.3.4 Bump vertx-core from 4.3.3 to 4.3.4
Bumps [pitest-maven](https://github.com/hcoles/pitest) from 1.9.5 to 1.9.6. - [Release notes](https://github.com/hcoles/pitest/releases) - [Commits](hcoles/pitest@1.9.5...1.9.6) --- updated-dependencies: - dependency-name: org.pitest:pitest-maven dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…test-pitest-maven-1.9.6 Bump pitest-maven from 1.9.5 to 1.9.6
Bumps [pitest-maven](https://github.com/hcoles/pitest) from 1.9.6 to 1.9.7. - [Release notes](https://github.com/hcoles/pitest/releases) - [Commits](hcoles/pitest@1.9.6...1.9.7) --- updated-dependencies: - dependency-name: org.pitest:pitest-maven dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…test-pitest-maven-1.9.7 Bump pitest-maven from 1.9.6 to 1.9.7
Bumps [pitest-maven](https://github.com/hcoles/pitest) from 1.9.7 to 1.9.8. - [Release notes](https://github.com/hcoles/pitest/releases) - [Commits](hcoles/pitest@1.9.7...1.9.8) --- updated-dependencies: - dependency-name: org.pitest:pitest-maven dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [micrometer-core](https://github.com/micrometer-metrics/micrometer) from 1.9.4 to 1.9.5. - [Release notes](https://github.com/micrometer-metrics/micrometer/releases) - [Commits](micrometer-metrics/micrometer@v1.9.4...v1.9.5) --- updated-dependencies: - dependency-name: io.micrometer:micrometer-core dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [dokka-maven-plugin](https://github.com/Kotlin/dokka) from 1.7.10 to 1.7.20. - [Release notes](https://github.com/Kotlin/dokka/releases) - [Commits](https://github.com/Kotlin/dokka/commits) --- updated-dependencies: - dependency-name: org.jetbrains.dokka:dokka-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…test-pitest-maven-1.9.8 Bump pitest-maven from 1.9.7 to 1.9.8
…rometer-micrometer-core-1.9.5 Bump micrometer-core from 1.9.4 to 1.9.5
…tbrains.dokka-dokka-maven-plugin-1.7.20 Bump dokka-maven-plugin from 1.7.10 to 1.7.20
Per the MP Metrics specification, if a `Metadata` object is constructed without the metric type and then used to create a metric of a specific type using `MetricRegistry` methods (such as `counter` or `gauge`), the metric type is set automatically. Since the `MicroProfileMetricsProvider` always uses the specific `MetricRegistry` methods (and never the generic method `register`), setting the metric type in `Metadata` is not necessary. Further, MP Metrics 5.0 removes the notion of `MetricType` altogether, but the rest of the `Metadata` API remains intact. This commit makes porting SmallRye Fault Tolerance to MP Metrics 5.0 much easier.
avoid explicitly setting metric type for MicroProfile Metrics
CI: Drop no longer last JDK GA (18) + move JDK 19 to GA + add next JD…
Small optimizations
The circuit breaker implementation used to perform state transitions only during invocations (that is, synchronously). This is easy to implement and doesn't affect correctness of the circuit breaker algorithm, so there's nothing wrong with it. However, SmallRye Fault Tolerance allows external observation of the circuit breaker state. With the existing implementation of state transitions only during invocations, such external observations would be correct when moving from closed to open and from half-open to closed (because these transitions are defined to happen as a result of an invocation), but would _not_ be correct when moving from open to half-open (which is defined to happen after certain amount of time, regardless of invocations). For example, if the circuit breaker is configured to transition from open to half-open after 5 seconds, but there are no invocations for 10 seconds, then external observers will see the circuit breaker staying open for twice the time it should be. With this commit, the synchronous transition from open to half-open is accompanied by an asynchronous, timer-based transition. This makes sure that even if there are no invocations, the circuit breaker will move from open to half-open correctly. The actual state transition is atomic CAS, so it doesn't matter that there are two threads trying to make the same transition at roughly the same time. Only one of them succeeds, and that will also emit the state transition event.
…e-transitions fix circuit breaker state transitions
release 5.6.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.