Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

2.13.1 backports 2 #28380

Merged
merged 12 commits into from Oct 4, 2022
Merged

2.13.1 backports 2 #28380

merged 12 commits into from Oct 4, 2022

Conversation

gsmet
Copy link
Member

@gsmet gsmet commented Oct 4, 2022

Please don't merge, I will merge it myself.

dependabot bot and others added 12 commits October 4, 2022 16:09
@dependabot @gsmet
Bump kafka3.version from 3.2.1 to 3.2.2
b2faa5c 
Bumps `kafka3.version` from 3.2.1 to 3.2.2.

Updates `kafka-clients` from 3.2.1 to 3.2.2

Updates `kafka-streams` from 3.2.1 to 3.2.2

Updates `kafka-streams-test-utils` from 3.2.1 to 3.2.2

Updates `kafka_2.13` from 3.2.1 to 3.2.2

---
updated-dependencies:
- dependency-name: org.apache.kafka:kafka-clients
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.apache.kafka:kafka-streams
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.apache.kafka:kafka-streams-test-utils
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.apache.kafka:kafka_2.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
(cherry picked from commit 06caa54)
@gsmet
Disable flaky SimpleContextPropagationTest.testArcMEContextPropagatio…
bd16766 
…nDisabled

(cherry picked from commit 5e6d6e8)
@dependabot @gsmet
Bump kafka3.version from 3.2.2 to 3.2.3
ac348f7 
Bumps `kafka3.version` from 3.2.2 to 3.2.3.

Updates `kafka-clients` from 3.2.2 to 3.2.3

Updates `kafka-streams` from 3.2.2 to 3.2.3

Updates `kafka-streams-test-utils` from 3.2.2 to 3.2.3

Updates `kafka_2.13` from 3.2.2 to 3.2.3

---
updated-dependencies:
- dependency-name: org.apache.kafka:kafka-clients
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.apache.kafka:kafka-streams
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.apache.kafka:kafka-streams-test-utils
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.apache.kafka:kafka_2.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
(cherry picked from commit 0b338ea)
@sberyozkin @gsmet
Disable flaky CodeFlowTest.testTokenautoRefresh
dcf4aa5 
(cherry picked from commit 454d4c9)
@sberyozkin @gsmet
Disable oidc-token-propagation-reactive test
b9785ee 
(cherry picked from commit cf5a277)
@gsmet
Disable OpenTelemetryReactiveClientTest#post() as flaky
65220a4 
(cherry picked from commit aed7fb7)
@gsmet
Disable all KafkaDevServicesContinuousTesting as flaky
46dca5a 
(cherry picked from commit 5c61376)
@Sgitario @gsmet
Kubernetes: Correct artifact path location
c649b74 
Adding dependencies like `quarkus-openshift` and `quarkus-kubernetes-config` might lead into running the kubernetes processor when the JAR file is not correct yet.

With these changes, we'll get always the correct artifact.
Fix quarkusio#28108

(cherry picked from commit 922948b)
@Sgitario @gsmet
Not to ignore the property quarkus.kubernetes.ports.<name>.protocol
44528a6 
Relates to quarkusio#28297

(cherry picked from commit 7b9a896)
@sberyozkin @gsmet
Restore the query when redirecting to the OIDC error path
44a769e 
(cherry picked from commit 50125bc)
@derlin @gsmet
Honour DOCKER_CONFIG env var in jib the same way as in jib-core
9946571 
Support for DOCKER_CONFIG has been added in quarkusio#27460. However, in jib,
the DOCKER_CONFIG should point to a directory containing a `config.json`,
while in the quarkus implementation it must point to the `config.json`
file itself. This is very confusing, especially since there is no
documentation.

This commit fixes the `JibProcessor`, so it behave exactly as described
in the jib documentation (see
https://github.com/GoogleContainerTools/jib/blob/master/jib-maven-plugin/README.md#authentication-methods).
That is, if `DOCKER_CONFIG` is set, it is expected to point to a folder
with a `config.json` file.

To keep backward compatibility, if `DOCKER_CONFIG` points to a file,
it will be left untouched.

See also `com.google.cloud.tools.jib.plugins.common.DefaultCredentialRetrievers.java`.

(cherry picked from commit d5e2991)
@andreas-eberle @gsmet
Update Kotlin to version 1.7.20
4a29d46 
(cherry picked from commit 71dd94d)
@gsmet gsmet added the area/infra internal and infrastructure related issues label Oct 4, 2022
@gsmet gsmet self-assigned this Oct 4, 2022
@quarkus-bot quarkus-bot bot added area/arc Issue related to ARC (dependency injection) area/dependencies Pull requests that update a dependency file area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/gradle Gradle area/jakarta area/kubernetes area/oidc area/reactive-messaging area/smallrye labels Oct 4, 2022
@quarkus-bot
Copy link

quarkus-bot bot commented Oct 4, 2022

Failing Jobs - Building 4a29d46

Status Name Step Failures Logs Raw logs
✔️ JVM Tests - JDK 11
✖ JVM Tests - JDK 11 Windows Build Failures Logs Raw logs
✔️ JVM Tests - JDK 17
✔️ JVM Tests - JDK 18

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 Windows #

- Failing: extensions/vertx/deployment 
! Skipped: extensions/agroal/deployment extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 338 more

📦 extensions/vertx/deployment

✖ io.quarkus.vertx.DuplicatedContextTest.testThatBlockingEventConsumersAreCalledOnDuplicatedContext - More details - Source on GitHub

(RECIPIENT_FAILURE,8185) io.smallrye.mutiny.TimeoutException
	at io.vertx.core.eventbus.Message.fail(Message.java:141)
	at io.quarkus.vertx.runtime.VertxRecorder$3$1$1.handle(VertxRecorder.java:122)

✖ io.quarkus.vertx.mdc.VertxMDCTest.mdc line 144 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <10> but was: <0>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

✖ io.quarkus.vertx.mdc.VertxMDCTest.mdcNonVertxThreadTest line 121 - More details - Source on GitHub

java.lang.AssertionError: 

Expected: a collection containing "Test MDC value ### Test 1"

@gsmet gsmet merged commit 1532056 into quarkusio:2.13 Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@gsmet gsmet

Labels
area/arc Issue related to ARC (dependency injection) area/dependencies Pull requests that update a dependency file area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/gradle Gradle area/infra internal and infrastructure related issues area/jakarta area/kubernetes area/oidc area/reactive-messaging area/smallrye
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
5 participants
@gsmet @sberyozkin @Sgitario @derlin @andreas-eberle