[NO_REVIEW] JAMES-2717 Run everything on docker ES #2343
Closed
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
chibenwa
changed the title
test this please |
trantienduchn
force-pushed
the
remove-embeddedES-full-tests
branch
2 times, most recently
from
b1e93e3 to
1332dec
Compare
trantienduchn
changed the title
trantienduchn
force-pushed
the
remove-embeddedES-full-tests
branch
from
1332dec to
dd13d1e
Compare
trantienduchn
changed the title
trantienduchn
force-pushed
the
remove-embeddedES-full-tests
branch
2 times, most recently
from
14aecc2 to
0631a35
Compare
Not so good |
|
Can you try to restart ES container let's say every 100 test, just to see? |
|
Or try closing the ES ClientProvider when shutting down James server - this is some kind of leak related to connection not being reused like it was done with the Embedded ES |
trantienduchn
force-pushed
the
remove-embeddedES-full-tests
branch
from
99e45cb to
4bd41b8
Compare
I tested and saw that the Update1: seems like the docker cassandra has been not available, and this log is generated which I can't see in other builds |
trantienduchn
force-pushed
the
remove-embeddedES-full-tests
branch
from
4bd41b8 to
425debc
Compare
|
trantienduchn
force-pushed
the
remove-embeddedES-full-tests
branch
from
435ba5e to
df30131
Compare
|
remember to create a ticket about the cassandra bulk operation bug |
|
trantienduchn
force-pushed
the
remove-embeddedES-full-tests
branch
from
df30131 to
0832c30
Compare
test this please |
|
good new :) test this please |
test this please |
|
the goal is achieved |
vttranlina
pushed a commit
to vttranlina/james-project
that referenced
this pull request
Jul 15, 2024
…er side data (linagora#2343) This could help in the case the operator reverses James to an older version that does not support the recently introduced TypeName. - PushSubscription/get and PushListener would not fail when TypeStateFactory parsing the unknown typename from DB - Deserialize StateChangeEvent would not fail leads to resilient handling of StateChangeEvent Meanwhile, parsing user input, we need to be strict.
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.
Just for testing, It's not meant to be merged