[jira] [Commented] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749764#comment-16749764 ] Francesco Mari commented on OAK-6749: - [~Csaba Varga], for the sake of completeness, can you describe

[jira] [Updated] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-6749: Fix Version/s: 1.10 > Segment-Tar standby sync fails with "in-memory" blobs present

[jira] [Updated] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-6749: Fix Version/s: 1.10.1 > Segment-Tar standby sync fails with "in-memory" blobs present

[jira] [Commented] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746313#comment-16746313 ] Francesco Mari commented on OAK-6749: - I fixed the issue at r1851619. I'm going to backport

[jira] [Commented] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746129#comment-16746129 ] Francesco Mari commented on OAK-6749: - I incorporated [~tmueller]'s suggestions - both the one given

[jira] [Updated] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-6749: Attachment: OAK-6749-02.patch > Segment-Tar standby sync fails with "in-memory"

Re: [Talk-es] Fwd: [Talk-GB] I have a philosophical question...

Gracias por todos los sevicios prestados. Quisiera darme de baja de tus publicaciones en el correo (Gmail), ?ayudame¿ Gracias denuevo Un Saludo Jesus Mª Armentia El jue., 17 ene. 2019 a las 9:53, Miguel Sevilla-Callejo () escribió: > > Hola, > > Reboto este mail desde la lista británica que me ha

[jira] [Commented] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745305#comment-16745305 ] Francesco Mari commented on OAK-6749: - The first version of the patch changes the logic to determine

[jira] [Updated] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-6749: Attachment: OAK-6749-01.patch > Segment-Tar standby sync fails with "in-memory"

[jira] [Commented] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745302#comment-16745302 ] Francesco Mari commented on OAK-6749: - I added another test at r1851551 to prove that inline binaries

[jira] [Commented] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745156#comment-16745156 ] Francesco Mari commented on OAK-6749: - In r1851533 and r1851535 I refactored the blob processing logic

[jira] [Assigned] (OAK-6749) Segment-Tar standby sync fails with "in-memory" blobs present in the source repo

[ https://issues.apache.org/jira/browse/OAK-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari reassigned OAK-6749: --- Assignee: Francesco Mari > Segment-Tar standby sync fails with "in-memory"

[jira] [Assigned] (OAK-5613) Test failure: segment.standby.ExternalSharedStoreIT.testProxyFlippedIntermediateByteChange2

[ https://issues.apache.org/jira/browse/OAK-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari reassigned OAK-5613: --- Assignee: Francesco Mari > Test fail

[jira] [Resolved] (OAK-5532) Test failure: segment.standby.ExternalSharedStoreIT/BrokenNetworkTest.test...

[ https://issues.apache.org/jira/browse/OAK-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-5532. - Resolution: Won't Fix This issue relates to a module that has been deprecated and dismissed. I

[jira] [Resolved] (OAK-4709) Test failure: ExternalPrivateStoreIT.testProxyFlippedIntermediateByte2

[ https://issues.apache.org/jira/browse/OAK-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-4709. - Resolution: Won't Fix This issue relates to a module that has been deprecated and dismissed. I

[jira] [Resolved] (OAK-5613) Test failure: segment.standby.ExternalSharedStoreIT.testProxyFlippedIntermediateByteChange2

[ https://issues.apache.org/jira/browse/OAK-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-5613. - Resolution: Duplicate > Test fail

[jira] [Assigned] (OAK-5532) Test failure: segment.standby.ExternalSharedStoreIT/BrokenNetworkTest.test...

[ https://issues.apache.org/jira/browse/OAK-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari reassigned OAK-5532: --- Assignee: Francesco Mari > Test failure: segment.standby.ExternalSharedStor

[jira] [Assigned] (OAK-4709) Test failure: ExternalPrivateStoreIT.testProxyFlippedIntermediateByte2

[ https://issues.apache.org/jira/browse/OAK-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari reassigned OAK-4709: --- Assignee: Francesco Mari > Test fail

[jira] [Resolved] (OAK-7719) CheckCommand should consistently use an alternative journal if specified

[ https://issues.apache.org/jira/browse/OAK-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7719. - Resolution: Fixed Fix Version/s: 1.9.14 Fixed at r1850238. > CheckCommand sho

[jira] [Resolved] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7914. - Resolution: Not A Problem Fix Version/s: (was: 1.6.16) > Cleanup updates the gc.

[jira] [Commented] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16717618#comment-16717618 ] Francesco Mari commented on OAK-7914: - [~rma61...@adobe.com], good to know. I'm going to resolve

Re: Why don't we move to Git?

Hi, On Tue, 11 Dec 2018 at 10:56, Davide Giannella wrote: > Does git change always HEAD? Even if you merge something that fits > "behind" HEAD. > Git always changes the head when a merge commit is performed. See [1] for more details about how merging works in Git. I hope I understood your

[jira] [Assigned] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari reassigned OAK-7914: --- Assignee: Francesco Mari > Cleanup updates the gc.log after a failed compact

[jira] [Updated] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7914: Fix Version/s: (was: 1.10) 1.6.16 > Cleanup updates the gc.log after a fai

[jira] [Updated] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7914: Affects Version/s: 1.6.15 > Cleanup updates the gc.log after a failed compact

[jira] [Commented] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714994#comment-16714994 ] Francesco Mari commented on OAK-7914: - [~rma61...@adobe.com], I'm not able to reproduce this issue

Re: Why don't we move to Git?

Hi, On Mon, 10 Dec 2018 at 15:19, Davide Giannella wrote: > Another point to keep in mind is the version number for diagnostic > builds[0]. So far we used the SVN revision which is unique and > incremental. This works perfectly in the OSGi world making sure any > diagnostic build will apply as

[jira] [Commented] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714735#comment-16714735 ] Francesco Mari commented on OAK-7914: - [~rma61...@adobe.com], I don't think that the issue is caused

Re: Why don't we move to Git?

Hi, On Mon, 10 Dec 2018 at 12:08, Julian Reschke wrote: > They already provide patches through Github, right? Those patches have the be brought back into SVN. This requires some manual work. It's not a lot, but it's not as seamless as it could be. > I don't see anything broken with the

Re: Why don't we move to Git?

Hi, On Mon, 10 Dec 2018 at 11:45, Robert Munteanu wrote: > - one repository for Oak or one repository per module (oak-commons, > oak-api, etc )? > I don't think we should change the structure of the repository during the migration. I would maintain one single repository for Oak. > - how does

[jira] [Commented] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714532#comment-16714532 ] Francesco Mari commented on OAK-7914: - [~mduerig], I think that this issue is related to OAK-5360

Why don't we move to Git?

Given the recent announcement about gitbox.apache.org, the seamless integration with GitHub, and the fact that many of us already work with Git in our daily workflow, what about moving our repositories to Git?

[jira] [Resolved] (OAK-7945) Document the recover-journal command

[ https://issues.apache.org/jira/browse/OAK-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7945. - Resolution: Fixed Fix Version/s: 1.9.13 Fixed at r1848302. > Document the recover-jour

[jira] [Created] (OAK-7945) Document the recover-journal command

Francesco Mari created OAK-7945: --- Summary: Document the recover-journal command Key: OAK-7945 URL: https://issues.apache.org/jira/browse/OAK-7945 Project: Jackrabbit Oak Issue Type

[jira] [Commented] (OAK-7457) "Covariant return type change detected" warnings with java10

[ https://issues.apache.org/jira/browse/OAK-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710356#comment-16710356 ] Francesco Mari commented on OAK-7457: - [~reschke], I fixed the Segment Store in OAK-7942. My solution

[jira] [Resolved] (OAK-7942) Fix covariant return type changes in ByteBuffer

[ https://issues.apache.org/jira/browse/OAK-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7942. - Resolution: Fixed Fix Version/s: 1.9.13 Fixed at r1848226. > Fix covariant return t

[jira] [Updated] (OAK-7942) Fix covariant return type changes in ByteBuffer

[ https://issues.apache.org/jira/browse/OAK-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7942: Attachment: OAK-7942-02.patch > Fix covariant return type changes in ByteBuf

[jira] [Commented] (OAK-7942) Fix covariant return type changes in ByteBuffer

[ https://issues.apache.org/jira/browse/OAK-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710310#comment-16710310 ] Francesco Mari commented on OAK-7942: - The second version of the patch incorporates [~mduerig]'s

[jira] [Commented] (OAK-7942) Fix covariant return type changes in ByteBuffer

[ https://issues.apache.org/jira/browse/OAK-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710285#comment-16710285 ] Francesco Mari commented on OAK-7942: - [~mduerig], thanks for reviewing. I will make {{Buffer}} final

[jira] [Commented] (OAK-7942) Fix covariant return type changes in ByteBuffer

[ https://issues.apache.org/jira/browse/OAK-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710161#comment-16710161 ] Francesco Mari commented on OAK-7942: - The first version of the patch wraps every usage of {{ByteBuffer

[jira] [Updated] (OAK-7942) Fix covariant return type changes in ByteBuffer

[ https://issues.apache.org/jira/browse/OAK-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7942: Attachment: OAK-7942-01.patch > Fix covariant return type changes in ByteBuf

[jira] [Created] (OAK-7942) Fix covariant return type changes in ByteBuffer

Francesco Mari created OAK-7942: --- Summary: Fix covariant return type changes in ByteBuffer Key: OAK-7942 URL: https://issues.apache.org/jira/browse/OAK-7942 Project: Jackrabbit Oak Issue Type

[jira] [Commented] (OAK-7234) Check for outdated journal at startup

[ https://issues.apache.org/jira/browse/OAK-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708955#comment-16708955 ] Francesco Mari commented on OAK-7234: - My biggest concern about this issue is how we frame the problem

[jira] [Resolved] (OAK-7866) Add tooling for recovering from an outdated journal

[ https://issues.apache.org/jira/browse/OAK-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7866. - Resolution: Fixed Fix Version/s: 1.9.13 > Add tooling for recovering from an outda

[jira] [Updated] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7914: Priority: Critical (was: Major) > Cleanup updates the gc.log after a failed compact

[jira] [Commented] (OAK-7934) Expose the number of segments as metric

[ https://issues.apache.org/jira/browse/OAK-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707242#comment-16707242 ] Francesco Mari commented on OAK-7934: - [~mduerig], actually I think you could compute both the segment

[jira] [Commented] (OAK-7933) Expose number of tar readers as metric

[ https://issues.apache.org/jira/browse/OAK-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707177#comment-16707177 ] Francesco Mari commented on OAK-7933: - [~mduerig], I added a comment on the commit in GitHub. > Exp

[jira] [Updated] (OAK-7867) Flush thread gets stuck when input stream of binaries block

[ https://issues.apache.org/jira/browse/OAK-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7867: Fix Version/s: 1.9.10 > Flush thread gets stuck when input stream of binaries bl

[jira] [Resolved] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7918. - Resolution: Fixed Fix Version/s: 1.9.13 Resolving this issue. The changes made so far

[jira] [Commented] (OAK-7922) Improve the operations and the reporting of the check command

[ https://issues.apache.org/jira/browse/OAK-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702902#comment-16702902 ] Francesco Mari commented on OAK-7922: - [~mduerig], thanks for your feedback. I agree on keeping

[jira] [Commented] (OAK-7922) Improve the operations and the reporting of the check command

[ https://issues.apache.org/jira/browse/OAK-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702158#comment-16702158 ] Francesco Mari commented on OAK-7922: - Since code is better than words, I fleshed out the strategy I

[jira] [Updated] (OAK-7922) Improve the operations and the reporting of the check command

[ https://issues.apache.org/jira/browse/OAK-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7922: Attachment: OAK-7922-01.patch > Improve the operations and the reporting of the check comm

[jira] [Resolved] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7878. - Resolution: Fixed Fix Version/s: 1.9.13 Fixed at r1847637. [~ahanikel], thanks for your

[jira] [Assigned] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari reassigned OAK-7878: --- Assignee: Francesco Mari (was: Axel Hanikel) > Add unit test for LoggingH

[jira] [Commented] (OAK-7922) Improve the operations and the reporting of the check command

[ https://issues.apache.org/jira/browse/OAK-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701812#comment-16701812 ] Francesco Mari commented on OAK-7922: - [~dulceanu], [~mduerig], I would really like your input

[jira] [Updated] (OAK-7922) Improve the operations and the reporting of the check command

[ https://issues.apache.org/jira/browse/OAK-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7922: Description: The check command allows a user to check for both the head and the checkpoints

[jira] [Created] (OAK-7922) Improve the operations and the reporting of the check command

Francesco Mari created OAK-7922: --- Summary: Improve the operations and the reporting of the check command Key: OAK-7922 URL: https://issues.apache.org/jira/browse/OAK-7922 Project: Jackrabbit Oak

Re: [Monitoring] - Provisioning StatisticsProvider in Oak

On Tue, 27 Nov 2018 at 11:45, Tommaso Teofili wrote: > After having dig into the code for a while I can see following options: > - have a dedicated OSGi service on the query side that can be then > polled in a static way from QueryEngineImpl in order to obtain such a > reference (see patch from

[jira] [Created] (OAK-7920) Clarify the definition of the overall good revision for the check command

Francesco Mari created OAK-7920: --- Summary: Clarify the definition of the overall good revision for the check command Key: OAK-7920 URL: https://issues.apache.org/jira/browse/OAK-7920 Project

[jira] [Deleted] (OAK-7920) Clarify the definition of the overall good revision for the check command

[ https://issues.apache.org/jira/browse/OAK-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari deleted OAK-7920: > Clarify the definition of the overall good revision for the check comm

[jira] [Commented] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700753#comment-16700753 ] Francesco Mari commented on OAK-7918: - I removed {{ConsistencyChecker}} at r1847567. The functionality

[jira] [Commented] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700636#comment-16700636 ] Francesco Mari commented on OAK-7918: - I committed the first version of the patch at r1847563

[jira] [Commented] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700544#comment-16700544 ] Francesco Mari commented on OAK-7918: - [~mduerig], thanks for the review. I'm going to commit

[jira] [Commented] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700517#comment-16700517 ] Francesco Mari commented on OAK-7918: - The fourth version of the patch implements the same short

[jira] [Updated] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7918: Attachment: OAK-7918-04.patch > Extract checking logic from ConsistencyChec

[jira] [Updated] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7918: Attachment: OAK-7918-03.patch > Extract checking logic from ConsistencyChec

[jira] [Commented] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700465#comment-16700465 ] Francesco Mari commented on OAK-7918: - The third version of the patch is equivalent to the second both

[jira] [Commented] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698967#comment-16698967 ] Francesco Mari commented on OAK-7918: - In the second version of the patch I rearranged the code

[jira] [Updated] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7918: Attachment: OAK-7918-02.patch > Extract checking logic from ConsistencyChec

[jira] [Commented] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697342#comment-16697342 ] Francesco Mari commented on OAK-7918: - {{CheckInvalidRepositoryTest#testLargeJournal}} seems to fail

[jira] [Commented] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697306#comment-16697306 ] Francesco Mari commented on OAK-7918: - The first version of the patch is an intermediate refactoring

[jira] [Updated] (OAK-7918) Extract checking logic from ConsistencyChecker

[ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7918: Attachment: OAK-7918-01.patch > Extract checking logic from ConsistencyChec

[jira] [Commented] (OAK-7866) Add tooling for recovering from an outdated journal

[ https://issues.apache.org/jira/browse/OAK-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697299#comment-16697299 ] Francesco Mari commented on OAK-7866: - Extracting the consistency check logic out

[jira] [Created] (OAK-7918) Extract checking logic from ConsistencyChecker

Francesco Mari created OAK-7918: --- Summary: Extract checking logic from ConsistencyChecker Key: OAK-7918 URL: https://issues.apache.org/jira/browse/OAK-7918 Project: Jackrabbit Oak Issue Type

[jira] [Commented] (OAK-7914) Cleanup updates the gc.log after a failed compaction

[ https://issues.apache.org/jira/browse/OAK-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695748#comment-16695748 ] Francesco Mari commented on OAK-7914: - [~mduerig], what do you think about this? > Cleanup upda

[jira] [Created] (OAK-7914) Cleanup updates the gc.log after a failed compaction

Francesco Mari created OAK-7914: --- Summary: Cleanup updates the gc.log after a failed compaction Key: OAK-7914 URL: https://issues.apache.org/jira/browse/OAK-7914 Project: Jackrabbit Oak Issue

[jira] [Commented] (OAK-7866) Add tooling for recovering from an outdated journal

[ https://issues.apache.org/jira/browse/OAK-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694803#comment-16694803 ] Francesco Mari commented on OAK-7866: - I committed a first implementation of the {{recover-journal

[jira] [Commented] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693296#comment-16693296 ] Francesco Mari commented on OAK-7878: - [~ahanikel], I'm assigning this issue to you until your next

[jira] [Assigned] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari reassigned OAK-7878: --- Assignee: Axel Hanikel (was: Francesco Mari) > Add unit test for LoggingH

[jira] [Commented] (OAK-7908) Backport and validate OAK-7867 to Oak 1.8

[ https://issues.apache.org/jira/browse/OAK-7908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693048#comment-16693048 ] Francesco Mari commented on OAK-7908: - The changes look good to me. > Backport and validate OAK-7

Re: Intent to backport OAK-7867 to Oak 1.8 and 1.6

+1 On Mon, 19 Nov 2018 at 17:50, Michael Dürig wrote: > Hi, > > I intend to backport OAK-7867 to Oak 1.8 and 1.6. This fixes an issue > that can cause sever data loss with the segment node store. There is a > medium to high risk with this backport as it touches some of the core > parts of the

[jira] [Commented] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686467#comment-16686467 ] Francesco Mari commented on OAK-7878: - [~ahanikel], I committed the most recent patch at r1846579

[jira] [Comment Edited] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686467#comment-16686467 ] Francesco Mari edited comment on OAK-7878 at 11/14/18 12:52 PM: [~ahanikel

[jira] [Updated] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7878: Fix Version/s: (was: 1.9.12) > Add unit test for LoggingH

[jira] [Updated] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7878: Attachment: OAK-7878-02.patch > Add unit test for LoggingH

[jira] [Commented] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676340#comment-16676340 ] Francesco Mari commented on OAK-7878: - [~ahanikel], the patch looks good but I think it could

[jira] [Assigned] (OAK-7878) Add unit test for LoggingHook

[ https://issues.apache.org/jira/browse/OAK-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari reassigned OAK-7878: --- Assignee: Francesco Mari > Add unit test for LoggingH

Re: [NTG-context] Font Awesome (again)

Hello! That was it, I forgot rule one: update your ConTeXt before asking questions. I updated to newest current and everything started working. Thank you, Mari On Thu, Nov 1, 2018 at 2:59 PM Wolfgang Schuster wrote: > > Hi Mari, > > you have to update your installation because f

[jira] [Resolved] (OAK-7877) Avoid unnecessary operations when logging read operations

[ https://issues.apache.org/jira/browse/OAK-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7877. - Resolution: Fixed Fix Version/s: 1.9.11 Fixed at r1845584. > Avoid unnecessary operati

[jira] [Commented] (OAK-7877) Avoid unnecessary operations when logging read operations

[ https://issues.apache.org/jira/browse/OAK-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673081#comment-16673081 ] Francesco Mari commented on OAK-7877: - These are the results for {{ConcurrentCreateNodeTest}} without

[jira] [Commented] (OAK-7877) Avoid unnecessary operations when logging read operations

[ https://issues.apache.org/jira/browse/OAK-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672947#comment-16672947 ] Francesco Mari commented on OAK-7877: - Currently compiling the benchmark runner, benchmarks

[jira] [Commented] (OAK-7877) Avoid unnecessary operations when logging read operations

[ https://issues.apache.org/jira/browse/OAK-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672934#comment-16672934 ] Francesco Mari commented on OAK-7877: - In the first version of the patch I wrapped the calls

[jira] [Updated] (OAK-7877) Avoid unnecessary operations when logging read operations

[ https://issues.apache.org/jira/browse/OAK-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7877: Attachment: OAK-7877-01.patch > Avoid unnecessary operations when logging read operati

[jira] [Created] (OAK-7877) Avoid unnecessary operations when logging read operations

Francesco Mari created OAK-7877: --- Summary: Avoid unnecessary operations when logging read operations Key: OAK-7877 URL: https://issues.apache.org/jira/browse/OAK-7877 Project: Jackrabbit Oak

[jira] [Resolved] (OAK-7874) Upgrade docker-junit-rule to version 2.2.2

[ https://issues.apache.org/jira/browse/OAK-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7874. - Resolution: Fixed Fix Version/s: 1.9.11 Fixed at r1845477. > Upgrade docker-junit-r

Re: Test failures in o.a.j.o.plugins.document

The problem seems to be caused by an incompatibility between the Docker client shipped with docker-junit-rule and the latest version of Docker. I created OAK-7874 to track this. On Thu, 1 Nov 2018 at 11:26, Francesco Mari wrote: > I experience multiple failures from te

[jira] [Created] (OAK-7874) Upgrade docker-junit-rule to version 2.2.2

Francesco Mari created OAK-7874: --- Summary: Upgrade docker-junit-rule to version 2.2.2 Key: OAK-7874 URL: https://issues.apache.org/jira/browse/OAK-7874 Project: Jackrabbit Oak Issue Type

[jira] [Resolved] (OAK-7873) Delete o.a.j.o.segment.util.RoleUtils

[ https://issues.apache.org/jira/browse/OAK-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7873. - Resolution: Fixed Fix Version/s: 1.9.11 Fixed at r1845461. > Del

[jira] [Created] (OAK-7873) Delete o.a.j.o.segment.util.RoleUtils

Francesco Mari created OAK-7873: --- Summary: Delete o.a.j.o.segment.util.RoleUtils Key: OAK-7873 URL: https://issues.apache.org/jira/browse/OAK-7873 Project: Jackrabbit Oak Issue Type

Re: [NTG-context] Font Awesome (again)

thereof, but couldn't get the symbol. What am I doing wrong? What have I missed? TIA, Mari On Sun, Oct 7, 2018 at 4:45 PM Wolfgang Schuster wrote: > > > > Aditya Mahajan schrieb am 07.10.18 um 15:26: > > Hi, > > > > There is a FontAwesome.otf file that is distributed w

<    1   2   3   4   5   6   7   8   9   10   >