Bump quarkus.version from 3.0.0.Final to 3.0.1.Final #161
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps `quarkus.version` from 3.0.0.Final to 3.0.1.Final. Updates `quarkus-bom` from 3.0.0.Final to 3.0.1.Final - [Release notes](https://github.com/quarkusio/quarkus/releases) - [Commits](quarkusio/quarkus@3.0.0.Final...3.0.1.Final) Updates `quarkus-maven-plugin` from 3.0.0.Final to 3.0.1.Final Updates `quarkus-extension-processor` from 3.0.0.Final to 3.0.1.Final Updates `quarkus-extension-maven-plugin` from 3.0.0.Final to 3.0.1.Final - [Release notes](https://github.com/quarkusio/quarkus/releases) - [Commits](quarkusio/quarkus@3.0.0.Final...3.0.1.Final) --- updated-dependencies: - dependency-name: io.quarkus:quarkus-bom dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: io.quarkus:quarkus-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: io.quarkus:quarkus-extension-processor dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: io.quarkus:quarkus-extension-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
|
Paging in @injectives and @gsmet and @maxandersen There are 2 reactive tests that fail since Quarkus 3.0.1 Here's one of them: The test: @Test
void getReactiveFruitsShouldWork() {
RestAssured.given()
.when().get("/reactivefruits/")
.then().statusCode(Status.OK.getStatusCode())
.statusCode(200)
.body(containsString("data:Apfel"));
}and the code under test: @GET
@Produces(MediaType.SERVER_SENT_EVENTS)
public Flow.Publisher<String> get() {
System.out.println("Hello");
// Create a stream from a resource we can close in a finalizer...
return Multi.createFrom().resource(() -> driver.session(ReactiveSession.class), // <.>
session -> session.executeRead(tx -> {
System.out.println("read executed");
var result = tx.run("MATCH (f:Fruit) RETURN f.name as name ORDER BY f.name");
return Multi.createFrom().publisher(result).flatMap(ReactiveResult::records)
.onItem().invoke(r -> {
System.out.println(r);
}).onCompletion().invoke(() -> {
System.out.println("records done");
});
}))
.withFinalizer(ReactiveFruitResource::sessionFinalizer) // <.>
.map(record -> record.get("name").asString());
}The code works perfectly fine with JVM and without any data present in the database both on native and JVM. However native starts to fail when there's data. I am a bit out of things I can try here. You need to build with Required database This works, as it has no data… Create some data and do the reactive test again… I See being logged and then the multi just does not complete. On JVM this works. |
|
Superseded by #164. |
|
The followup does not change things. |
This was referenced May 3, 2023
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.
Bumps
quarkus.versionfrom 3.0.0.Final to 3.0.1.Final.Updates
quarkus-bomfrom 3.0.0.Final to 3.0.1.FinalRelease notes
Sourced from quarkus-bom's releases.
... (truncated)
Commits
eef6e01[RELEASE] - Bump version to 3.0.1.Finalde7076dCreate update guide68a4be8PLANNER-2861 Upgrate to OptaPlanner 989cd51cMerge pull request #32878 from Sanne/backportsWithVertxAndHrc35fda7Update to Vert.x 4.4.189e7933Upgrade to Hibernate Reactive 2.0.0.CR14d50319implement the config filter by extension8a766efMake dev-services hot reload706f084Disable DEV UI for remote dev modee647665Dev UI Fix labels not clearing outUpdates
quarkus-maven-pluginfrom 3.0.0.Final to 3.0.1.FinalUpdates
quarkus-extension-processorfrom 3.0.0.Final to 3.0.1.FinalUpdates
quarkus-extension-maven-pluginfrom 3.0.0.Final to 3.0.1.FinalRelease notes
Sourced from quarkus-extension-maven-plugin's releases.
... (truncated)
Commits
eef6e01[RELEASE] - Bump version to 3.0.1.Finalde7076dCreate update guide68a4be8PLANNER-2861 Upgrate to OptaPlanner 989cd51cMerge pull request #32878 from Sanne/backportsWithVertxAndHrc35fda7Update to Vert.x 4.4.189e7933Upgrade to Hibernate Reactive 2.0.0.CR14d50319implement the config filter by extension8a766efMake dev-services hot reload706f084Disable DEV UI for remote dev modee647665Dev UI Fix labels not clearing outDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)