[jira] [Created] (OAK-10314) Build Jackrabbit/jackrabbit-oak-trunk #1003 failed
Hudson created OAK-10314: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1003 failed Key: OAK-10314 URL: https://issues.apache.org/jira/browse/OAK-10314 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1003 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1003|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1003/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1003/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10307) oak-shaded-guava leaks original guava as transitive dependency
[ https://issues.apache.org/jira/browse/OAK-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733315#comment-17733315 ] Julian Reschke edited comment on OAK-10307 at 6/19/23 5:43 PM: --- trunk: [7a0b459dc4|https://github.com/apache/jackrabbit-oak/commit/7a0b459dc46ef649d45bad003c120df67e337e5a] [91d10c9f71|https://github.com/apache/jackrabbit-oak/commit/91d10c9f7133d3fee5b9a8738c651d4620a2a361] [8dc7950337|https://github.com/apache/jackrabbit-oak/commit/8dc79503376890a0d9ed5e7a602a6e380e2a0113] [a02cbb9d0b|https://github.com/apache/jackrabbit-oak/commit/a02cbb9d0b221260d240f2f81571b1d10db60502] [1d6581bb10|https://github.com/apache/jackrabbit-oak/commit/1d6581bb10b5d23f639b52da57eb41013b000d2f] was (Author: reschke): trunk: [91d10c9f71|https://github.com/apache/jackrabbit-oak/commit/91d10c9f7133d3fee5b9a8738c651d4620a2a361] [8dc7950337|https://github.com/apache/jackrabbit-oak/commit/8dc79503376890a0d9ed5e7a602a6e380e2a0113] [a02cbb9d0b|https://github.com/apache/jackrabbit-oak/commit/a02cbb9d0b221260d240f2f81571b1d10db60502] [1d6581bb10|https://github.com/apache/jackrabbit-oak/commit/1d6581bb10b5d23f639b52da57eb41013b000d2f] > oak-shaded-guava leaks original guava as transitive dependency > -- > > Key: OAK-10307 > URL: https://issues.apache.org/jira/browse/OAK-10307 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: shaded-guava >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Major > Fix For: 1.54.0 > > > oak-shaded-guava currently declares a compile dependency on original guava. > This means modules using oak-shaded-guava will transitively get original > guava and mistakingly use classes from there. > {noformat} > $ mvn dependency:tree -pl :oak-shaded-guava > [INFO] Scanning for projects... > [INFO] > [INFO] ---< org.apache.jackrabbit:oak-shaded-guava > >--- > [INFO] Building Jackrabbit Guava Wrapper 1.53-SNAPSHOT > [INFO] from pom.xml > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- dependency:3.4.0:tree (default-cli) @ oak-shaded-guava --- > [INFO] org.apache.jackrabbit:oak-shaded-guava:bundle:1.53-SNAPSHOT > [INFO] +- com.google.guava:guava:jar:32.0.1-jre:compile > [INFO] | +- com.google.guava:failureaccess:jar:1.0.1:compile > [INFO] | +- > com.google.guava:listenablefuture:jar:.0-empty-to-avoid-conflict-with-guava:compile > [INFO] | +- com.google.code.findbugs:jsr305:jar:3.0.2:compile > [INFO] | +- org.checkerframework:checker-qual:jar:3.33.0:compile > [INFO] | +- com.google.errorprone:error_prone_annotations:jar:2.18.0:compile > [INFO] | \- com.google.j2objc:j2objc-annotations:jar:2.8:compile > [INFO] +- org.osgi:org.osgi.annotation:jar:6.0.0:provided > [INFO] \- org.jetbrains:annotations:jar:18.0.0:provided > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10307) oak-shaded-guava leaks original guava as transitive dependency
[ https://issues.apache.org/jira/browse/OAK-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10307. -- Resolution: Fixed > oak-shaded-guava leaks original guava as transitive dependency > -- > > Key: OAK-10307 > URL: https://issues.apache.org/jira/browse/OAK-10307 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: shaded-guava >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Major > Fix For: 1.54.0 > > > oak-shaded-guava currently declares a compile dependency on original guava. > This means modules using oak-shaded-guava will transitively get original > guava and mistakingly use classes from there. > {noformat} > $ mvn dependency:tree -pl :oak-shaded-guava > [INFO] Scanning for projects... > [INFO] > [INFO] ---< org.apache.jackrabbit:oak-shaded-guava > >--- > [INFO] Building Jackrabbit Guava Wrapper 1.53-SNAPSHOT > [INFO] from pom.xml > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- dependency:3.4.0:tree (default-cli) @ oak-shaded-guava --- > [INFO] org.apache.jackrabbit:oak-shaded-guava:bundle:1.53-SNAPSHOT > [INFO] +- com.google.guava:guava:jar:32.0.1-jre:compile > [INFO] | +- com.google.guava:failureaccess:jar:1.0.1:compile > [INFO] | +- > com.google.guava:listenablefuture:jar:.0-empty-to-avoid-conflict-with-guava:compile > [INFO] | +- com.google.code.findbugs:jsr305:jar:3.0.2:compile > [INFO] | +- org.checkerframework:checker-qual:jar:3.33.0:compile > [INFO] | +- com.google.errorprone:error_prone_annotations:jar:2.18.0:compile > [INFO] | \- com.google.j2objc:j2objc-annotations:jar:2.8:compile > [INFO] +- org.osgi:org.osgi.annotation:jar:6.0.0:provided > [INFO] \- org.jetbrains:annotations:jar:18.0.0:provided > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10312) Build Jackrabbit/jackrabbit-oak-trunk #1001 failed
[ https://issues.apache.org/jira/browse/OAK-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17734296#comment-17734296 ] Hudson commented on OAK-10312: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1002|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1002/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1002/console] > Build Jackrabbit/jackrabbit-oak-trunk #1001 failed > -- > > Key: OAK-10312 > URL: https://issues.apache.org/jira/browse/OAK-10312 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1001 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1001|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1001/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1001/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10313) Identify revisions created by late-write scenario
[ https://issues.apache.org/jira/browse/OAK-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17734218#comment-17734218 ] Marcel Reutegger commented on OAK-10313: Created new tests in WriteAfterRecoveryTest similar to those in OAK-10254, but using the existing FailingDocumentStore (with some enhancements) to simulate 'late-write' scenarios for various content changes. The consistency check takes a root node state and a NodeDocument and identifies change revisions that are not visible when traversing to the node state represented by the given NodeDocument even though they should be given the head revision on the root node state. Proposed changed in https://github.com/apache/jackrabbit-oak/pull/995 > Identify revisions created by late-write scenario > - > > Key: OAK-10313 > URL: https://issues.apache.org/jira/browse/OAK-10313 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk, run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > > OAK-10254 describes a 'late-write' scenario where a DocumentNodeStore is > writing some changes after its lease timed out. > Introduce a consistency check that identifies those revisions on a > NodeDocument. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10313) Identify revisions created by late-write scenario
Marcel Reutegger created OAK-10313: -- Summary: Identify revisions created by late-write scenario Key: OAK-10313 URL: https://issues.apache.org/jira/browse/OAK-10313 Project: Jackrabbit Oak Issue Type: Task Components: documentmk, run Reporter: Marcel Reutegger Assignee: Marcel Reutegger OAK-10254 describes a 'late-write' scenario where a DocumentNodeStore is writing some changes after its lease timed out. Introduce a consistency check that identifies those revisions on a NodeDocument. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10312) Build Jackrabbit/jackrabbit-oak-trunk #1001 failed
Hudson created OAK-10312: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1001 failed Key: OAK-10312 URL: https://issues.apache.org/jira/browse/OAK-10312 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1001 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1001|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1001/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1001/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9957) Upgrade to tika1.28.5
[ https://issues.apache.org/jira/browse/OAK-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-9957: Summary: Upgrade to tika1.28.5 (was: Upgrade to jira 1.28.5) > Upgrade to tika1.28.5 > - > > Key: OAK-9957 > URL: https://issues.apache.org/jira/browse/OAK-9957 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Nitin Gupta >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10311) Optimize SegmentBlob#equals for segment blobs that originate from the same blob store
Axel Hanikel created OAK-10311: -- Summary: Optimize SegmentBlob#equals for segment blobs that originate from the same blob store Key: OAK-10311 URL: https://issues.apache.org/jira/browse/OAK-10311 Project: Jackrabbit Oak Issue Type: Story Components: segment-tar Affects Versions: 1.52.0 Reporter: Axel Hanikel Fix For: 1.54.0 [SegmentBlob#equals|https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.52.0/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/SegmentBlob.java] can be optimized for blobs originating from the same external blob store: In that case, SegmentBlob#getBlobId() can be used to determine if the blobs are equal or not. That change should avoid falling back to a byte-by-byte comparison if the two blobs aren't equal and therefore don't have the same ContentIdentity, which can be very expensive for larger blobs. The optimization should be placed behind a code/feature toggle or system property and disabled by default. The reason is that the contract of [Blob#getContentIdentity|https://github.com/apache/jackrabbit-oak/blob/cc0521e1cf8dc10ad7a8d41a9f2d3fd2905e5c9b/oak-api/src/main/java/org/apache/jackrabbit/oak/api/Blob.java#L80-L82] does not mention the special case where Blobs reside in the same blob store. As part of this story, integration and benchmark tests should be created to demonstrate gains in performance and correct behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10310) Bump testcontainers dependency to v1.18.3
[ https://issues.apache.org/jira/browse/OAK-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Fortino resolved OAK-10310. Fix Version/s: 1.54.0 Resolution: Fixed > Bump testcontainers dependency to v1.18.3 > - > > Key: OAK-10310 > URL: https://issues.apache.org/jira/browse/OAK-10310 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: parent >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Minor > Fix For: 1.54.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10308) Tests using MongoUtils may skip even if Docker is available
[ https://issues.apache.org/jira/browse/OAK-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-10308. Fix Version/s: 1.54.0 Resolution: Fixed Merged PR. > Tests using MongoUtils may skip even if Docker is available > --- > > Key: OAK-10308 > URL: https://issues.apache.org/jira/browse/OAK-10308 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.54.0 > > > MongoUtil first tries to connect to an already running MongoDB on the default > port and then tries to start MongoDB in docker. The latter may fail even when > docker is available and MongoDB is started successfully. > The host for the constructed connection URI is hardcoded to 'localhost', > which may not work when docker exposed MongoDB on 127.0.0.1: -- This message was sent by Atlassian Jira (v8.20.10#820010)