-
-
Notifications
You must be signed in to change notification settings - Fork 179
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.
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
[6.x.x] Fix errors on update operations #5296
Conversation
@line-o The outstanding issues need to be addressed first please - #5276 (comment) |
The test is different from the one in the original PR targeted at develop. |
Okay, but develop needs to be fixed first... Then those same commits can either be in this PR, or in a separate PR to 6.x.x. |
Please see the actual test that is part of the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR (#5296) is a backport to 6.x.x of #5276 (which targeted develop
). My concern is that #5276 was rushed and merged into develop
whilst reviews were still identifying issues. This has led to #5276 actually introducing problems into develop
by leaking resources in its tests. I asked for this to be fixed in April 2024 in both PRs. This has not yet been done. As this PR (#5296) is a backport, it has the same leak issues as #5276 and so cannot yet be merged.
To resolve this, the author (as I have requested), or anyone, needs to:
- send a new PR to
develop
to fix the resource leak problems introduced by Fix errors on update operations #5276 - get that new PR through review and then merged.
- append the bugfix commit(s) from that new PR into this PR ([6.x.x] Fix errors on update operations #5296).
- we can then re-review this PR ([6.x.x] Fix errors on update operations #5296) and hopefully get it merged.
88f83a9
to
a71f09b
Compare
exist-core/src/test/java/org/exist/xquery/update/UpdateInsertTriggersDefrag.java
Outdated
Show resolved
Hide resolved
This PR has now the needed approvals of two members of the core-team. |
This can be considered a fix - the tests do differ between version 6 and 7 because of the breaking changes in XML-DB API |
|
414b1b6
to
b6d2466
Compare
- add constructor to ExistXmldbEmbeddedServer that allows passing in configuration properties - create new test that updates a document with fragmentation limit set to -1
A regression introduced in c553667 causes a NullPointerException to be thrown whenever an XML-resource needs to be defragmented. This will be triggered on frequent writes to any XML-resource and will effectively remove the file from the database and from any indexes.
… tests unless we are intending to explicitly test the XML:DB API implementation
b6d2466
to
6955588
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This now with my additions looks correct.
Backport of #5276
refs #5273