[
https://issues.apache.org/jira/browse/OAK-7872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7872.
-
Resolution: Fixed
Fix Version/s: 1.9.10
Fixed at r1845440.
> Make LoggingHook priv
Francesco Mari created OAK-7872:
---
Summary: Make LoggingHook private to o.a.j.o.segment
Key: OAK-7872
URL: https://issues.apache.org/jira/browse/OAK-7872
Project: Jackrabbit Oak
Issue Type
[
https://issues.apache.org/jira/browse/OAK-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7864.
-
Resolution: Fixed
Fix Version/s: 1.9.10
1.10
Fixed at r1845437
I experience multiple failures from tests in o.a.j.o.plugins.document. It
looks like they have something to do with how the tests use Docker. I have
Docker for Mac installed and working on my machine. Can somebody help with
this?
A sample of failures is the following:
[INFO] Running
[
https://issues.apache.org/jira/browse/OAK-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671397#comment-16671397
]
Francesco Mari commented on OAK-7864:
-
[~ahanikel], the patch looks good to me and I'm going to commit
+1
On Tue, 30 Oct 2018 at 14:03, Michael Dürig wrote:
>
>
> Hi,
>
> I intend to backport https://issues.apache.org/jira/browse/OAK-7838.
> This fixes an unclosed executor (by removing it). The fix only affects
> monitoring code and is thus rather low risk.
>
>
> Michael
>
[
https://issues.apache.org/jira/browse/OAK-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668371#comment-16668371
]
Francesco Mari commented on OAK-5885:
-
[~mduerig], since the description mentions listing candidates
[
https://issues.apache.org/jira/browse/OAK-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668299#comment-16668299
]
Francesco Mari commented on OAK-7867:
-
[~mduerig], the patch looks good to me. I particularly like
[
https://issues.apache.org/jira/browse/OAK-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667362#comment-16667362
]
Francesco Mari commented on OAK-7867:
-
[~mduerig], another alternative would be to make
Francesco Mari created OAK-7866:
---
Summary: Add tooling for recovering from an outdated journal
Key: OAK-7866
URL: https://issues.apache.org/jira/browse/OAK-7866
Project: Jackrabbit Oak
Issue
[
https://issues.apache.org/jira/browse/OAK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665199#comment-16665199
]
Francesco Mari edited comment on OAK-7849 at 10/26/18 1:55 PM:
---
Sure, I
[
https://issues.apache.org/jira/browse/OAK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665199#comment-16665199
]
Francesco Mari commented on OAK-7849:
-
Sure, I will assign that issue to myself to keep in under my
[
https://issues.apache.org/jira/browse/OAK-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari reassigned OAK-7864:
---
Assignee: Francesco Mari
> Recording read operations to the segment st
[
https://issues.apache.org/jira/browse/OAK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7849.
-
Resolution: Fixed
Fix Version/s: 1.9.10
1.10
Committed at r1844899
[
https://issues.apache.org/jira/browse/OAK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari reassigned OAK-7849:
---
Assignee: Francesco Mari
> CommitHook for recording write operations to the segment st
[
https://issues.apache.org/jira/browse/OAK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665067#comment-16665067
]
Francesco Mari edited comment on OAK-7849 at 10/26/18 11:40 AM:
[~ahanikel
[
https://issues.apache.org/jira/browse/OAK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665067#comment-16665067
]
Francesco Mari commented on OAK-7849:
-
[~ahanikel], I'm not an expert of Sling Logging
[
https://issues.apache.org/jira/browse/OAK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662274#comment-16662274
]
Francesco Mari commented on OAK-7849:
-
[~ahanikel], the patch looks much better now. In order
[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1666#comment-1666
]
Francesco Mari commented on OAK-7846:
-
The second version of the patch redefines the export format
[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7846:
Attachment: OAK-7846-02.patch
> Add a tool to export the tree pointed to by a node rec
+1
On Wed, 24 Oct 2018 at 11:42, Michael Dürig wrote:
>
> Hi,
>
> I intend to backport https://issues.apache.org/jira/browse/OAK-7837.
> This is a simple fix in tooling (oak-run check) preventing it from crash
> under certain circumstances. The fix is simple and the risk is low.
>
> Michael
>
+1
On Wed, 24 Oct 2018 at 11:46, Michael Dürig wrote:
>
> Hi,
>
> I intend to backport https://issues.apache.org/jira/browse/OAK-7854.
> This issues adds and additional monitoring endpoint to detect the case
> where the flush thread fails. Although the fix affects the file store,
> the changes
[
https://issues.apache.org/jira/browse/OAK-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660539#comment-16660539
]
Francesco Mari commented on OAK-7854:
-
I'm in favour with the approach implemented
[
https://issues.apache.org/jira/browse/OAK-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660556#comment-16660556
]
Francesco Mari commented on OAK-7854:
-
[~mduerig], LGTM.
> Add liveliness monitoring for FileSt
[
https://issues.apache.org/jira/browse/OAK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659054#comment-16659054
]
Francesco Mari commented on OAK-7849:
-
[~ahanikel], thanks for the patch! I suggest some improvements
[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658962#comment-16658962
]
Francesco Mari commented on OAK-7846:
-
As a proof of concept I implemented a first draft of the command
[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7846:
Attachment: OAK-7846-01.patch
> Add a tool to export the tree pointed to by a node rec
[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658960#comment-16658960
]
Francesco Mari commented on OAK-7846:
-
[~mduerig], the format above is processable with a finite state
[
https://issues.apache.org/jira/browse/OAK-7853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658892#comment-16658892
]
Francesco Mari commented on OAK-7853:
-
[~mduerig], your analysis seems right to me. The patch looks
[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653894#comment-16653894
]
Francesco Mari commented on OAK-7846:
-
[~ahanikel], some encoding for the property values is definitely
[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653807#comment-16653807
]
Francesco Mari commented on OAK-7846:
-
The tool receives as input one or more IDs of node records
Francesco Mari created OAK-7846:
---
Summary: Add a tool to export the tree pointed to by a node record
Key: OAK-7846
URL: https://issues.apache.org/jira/browse/OAK-7846
Project: Jackrabbit Oak
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7834.
-
Resolution: Fixed
I renamed the command to {{search-nodes}} at r1844073.
> Add a tool to ident
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari reopened OAK-7834:
-
[~mduerig], you are right. I would go for {{node-search}}, since this is
exactly what the command
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7834.
-
Resolution: Fixed
Fix Version/s: 1.9.10
Fixed at 1844005.
> Add a tool to identify su
.10.2018 um 09:04 schrieb IK1HJS Carlo De Mari:
[snipped]
Hi Carlo!
In my opinion I would prefer 73's from both partners as confirmation of
the QSO. Only then a QSO (in digital modes) is to be classified as being
complete for me.
vy73
Enrico, OE1EQW
_
Dear Ecolog-L,
We seek a highly motivated scientist to work on a three year BMBF-funded
research project EMSAfrica, in which there is financial support for a
75% position. The research is based in South Africa and the place of
work is the Chair of Plant Ecology at the University of Bayreuth,
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651371#comment-16651371
]
Francesco Mari commented on OAK-7834:
-
The third version of the patch adds a {{--output}} option
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7834:
Attachment: OAK-7834-03.patch
> Add a tool to identify super-root no
Gary, you didn't say your opinion on the subject. Why don't you dropp
off immediately instead of "SHOUTING" your statements ?
Do you think that everybody is always interested in all subjects of the
list ? The subject is perfectly in the object of the list, and nobody
complains ... it seems
Billit's up the the other operator to have the report, not you to
make sure that your report has been received ok.
I've sent my report and if he hasn't got it he will ask again...
I have his call and report, for me the qso is ok. A lot of contacts are
"not in log" or with wrong reports
Hi to all, I've just got into the reflector. I understand that In FT8
you usually use pre-compiled messages and , although it's possible,
nobody sends private messeges out of pre-compiled usually.
This means that the purpose of this mode is to make quick qso's in the
shortest time possible.
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650288#comment-16650288
]
Francesco Mari commented on OAK-7834:
-
The second version of the patch modifies the output
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7834:
Attachment: OAK-7834-02.patch
> Add a tool to identify super-root no
[
https://issues.apache.org/jira/browse/OAK-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650151#comment-16650151
]
Francesco Mari commented on OAK-7828:
-
[~dulceanu], LGTM.
> Log off heap access for segments w
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650146#comment-16650146
]
Francesco Mari commented on OAK-7834:
-
The first version of the patch implements a {{search}} command
[
https://issues.apache.org/jira/browse/OAK-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7834:
Attachment: OAK-7834-01.patch
> Add a tool to identify super-root no
Francesco Mari created OAK-7834:
---
Summary: Add a tool to identify super-root nodes
Key: OAK-7834
URL: https://issues.apache.org/jira/browse/OAK-7834
Project: Jackrabbit Oak
Issue Type: New
I've never tested it in Pharo 7, anyway if I am not wrong, Jupytertalk
doesn't save any file.
Be sure it is not a problem about Pharo 7 permissions.
El vie., 5 oct. 2018 11:49, H. Hirzel escribió:
> Hello Jesus Mari
>
> I am doing a new installation of JupyterTalk in a Pharo7 en
+1
On Thu, 4 Oct 2018 at 11:43, Michael Dürig wrote:
>
> Hi,
>
> With more work going into the Azure Segment Store, should we start
> tracking this via a dedicated Jira component?
>
> If there are no objections I suggest to add a segment-azure component.
>
> Michael
>
[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7788:
Fix Version/s: 1.9.9
> Measure read rate for the Segment St
[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7788.
-
Resolution: Fixed
Fixed at r1842607.
> Measure read rate for the Segment St
[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634081#comment-16634081
]
Francesco Mari commented on OAK-7788:
-
[~mduerig], before coming up with this patch I tried to create
[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633685#comment-16633685
]
Francesco Mari commented on OAK-7788:
-
[~mduerig], my bad. I removed the wrong patch and attached
[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7788:
Attachment: OAK-7788-01.patch
> Measure read rate for the Segment St
[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7788:
Attachment: (was: OAK-7755-01.patch)
> Measure read rate for the Segment St
[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16631744#comment-16631744
]
Francesco Mari commented on OAK-7788:
-
The first version of the patch register a new meter
[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7788:
Attachment: OAK-7755-01.patch
> Measure read rate for the Segment St
Francesco Mari created OAK-7788:
---
Summary: Measure read rate for the Segment Store
Key: OAK-7788
URL: https://issues.apache.org/jira/browse/OAK-7788
Project: Jackrabbit Oak
Issue Type
[
https://issues.apache.org/jira/browse/OAK-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625679#comment-16625679
]
Francesco Mari commented on OAK-7755:
-
I'm not aware of any issues on the Segment Store in the 1.6
[
https://issues.apache.org/jira/browse/OAK-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16621833#comment-16621833
]
Francesco Mari commented on OAK-7773:
-
[~mduerig], it looks very interesting. I would really like
[
https://issues.apache.org/jira/browse/OAK-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7755.
-
Resolution: Fixed
Fix Version/s: 1.6.15
Fixed at r1841442.
> deadlock TarMK flush, luc
[
https://issues.apache.org/jira/browse/OAK-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16621644#comment-16621644
]
Francesco Mari commented on OAK-7755:
-
[~mduerig], the purpose is to protect both {{tarWriter
[
https://issues.apache.org/jira/browse/OAK-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619018#comment-16619018
]
Francesco Mari commented on OAK-7755:
-
The first version of the patch extracts {{readGraphReferences
[
https://issues.apache.org/jira/browse/OAK-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7755:
Attachment: OAK-7755-01.patch
> deadlock TarMK flush, luc
[
https://issues.apache.org/jira/browse/OAK-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari reassigned OAK-7755:
---
Assignee: Francesco Mari
> deadlock TarMK flush, luc
[
https://issues.apache.org/jira/browse/OAK-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618766#comment-16618766
]
Francesco Mari commented on OAK-7755:
-
This kind of deadlock can't happen in the current version
[
https://issues.apache.org/jira/browse/OAK-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7755:
Description:
We are getting the following deadlock. Please help! (Production environment)
I have
[
https://issues.apache.org/jira/browse/OAK-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618667#comment-16618667
]
Francesco Mari commented on OAK-7761:
-
[~mduerig], LGTM.
> SegmentTarWriter#readSegment does not ch
[
https://issues.apache.org/jira/browse/OAK-7762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618664#comment-16618664
]
Francesco Mari commented on OAK-7762:
-
[~mduerig], LGTM.
> Store segments off heap when memory mapp
[
https://issues.apache.org/jira/browse/OAK-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618655#comment-16618655
]
Francesco Mari commented on OAK-7760:
-
[~mduerig], I think that {{readFully}} should return early from
[
https://issues.apache.org/jira/browse/OAK-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610578#comment-16610578
]
Francesco Mari commented on OAK-7747:
-
With this issue I didn't want to define a release environment
[
https://issues.apache.org/jira/browse/OAK-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7747:
Attachment: OAK-7747-01.patch
> Use Docker to define the development environm
Francesco Mari created OAK-7747:
---
Summary: Use Docker to define the development environment
Key: OAK-7747
URL: https://issues.apache.org/jira/browse/OAK-7747
Project: Jackrabbit Oak
Issue Type
[
https://issues.apache.org/jira/browse/OAK-7722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610352#comment-16610352
]
Francesco Mari commented on OAK-7722:
-
[~mduerig], I think the patch looks good. If the need arises, we
[
https://issues.apache.org/jira/browse/OAK-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-6890:
Fix Version/s: 1.6.14
> Background threads might not be automatically restar
[
https://issues.apache.org/jira/browse/OAK-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605438#comment-16605438
]
Francesco Mari commented on OAK-6890:
-
Backported to 1.6 at r1840193.
> Background threads mi
be fixed.
Thank you everybody for your help,
Mari
On Wed, Sep 5, 2018 at 5:40 PM Pablo Rodriguez wrote:
>
> On 09/04/2018 10:40 PM, Henning Hraban Ramm wrote:
> > [...]
> > Hans investigated and could trace my problem to an Acrobat bug (or at
> > least it doesn't adhere to the P
I intend to backport OAK-6890 to the 1.6 branch. The keeps some background
threads alive in the face of unexpected failures. All of these threads are
critical for the correctness of the Segment Store.
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604148#comment-16604148
]
Francesco Mari commented on OAK-7721:
-
Backported to 1.6 at r1840106.
> Records of specific size br
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7721:
Fix Version/s: 1.6.14
> Records of specific size bring SegmentBufferWriter#flush to f
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604089#comment-16604089
]
Francesco Mari commented on OAK-7721:
-
Backported to 1.8 at r1840098.
> Records of specific size br
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7721:
Fix Version/s: 1.8.8
> Records of specific size bring SegmentBufferWriter#flush to f
I intend to backport OAK-7721 to the 1.8 and 1.6 branches. The fix prevents
the segment buffers from being corrupted when too big records are
persisted. The corruption is only detected when the buffer is flushed to
disk, when it's too late to detect the code path that led to the
corruption. The
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7721.
-
Resolution: Fixed
Fix Version/s: 1.9.9
Fixed at r1840024.
> Records of specific size br
thought adding something to
\externalfigure might do the trick, but there doesn't seem to be a
suitable key.
Thanks,
Mari
cropping_problem.pdf
Description: Adobe PDF document
cropping_problem.tex
Description: Binary data
ex.pdf
Description: Adobe PDF document
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602039#comment-16602039
]
Francesco Mari commented on OAK-7721:
-
[~mduerig], the third version of the patch adds a comment
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7721:
Attachment: OAK-7721-03.patch
> Records of specific size bring SegmentBufferWriter#flush to f
On Thu, Aug 30, 2018 at 2:40 PM Hans Hagen wrote:
> don't use t-simplefonts, use \selectfont instead (its replacement)
I can't find \selectfont on the wiki, can I get an example on the
usage? My attempts haven't been successful, there's probably something
I don't understand.
M
he moment I have it on Linux and that is fine.
>
> I am now more interested in actually USING it.
>
> See my question about giving back SVG graphics results
>
>
> On 8/29/18, Jesus Mari Aguirre wrote:
> > I think Windows will not be possible by now, there's not Pharo 6
[
https://issues.apache.org/jira/browse/OAK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7720:
Fix Version/s: 1.6.14
> Log hex dump of too big segme
[
https://issues.apache.org/jira/browse/OAK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598758#comment-16598758
]
Francesco Mari commented on OAK-7720:
-
Backported to 1.6 at r1839760.
> Log hex dump of too
[
https://issues.apache.org/jira/browse/OAK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7720:
Fix Version/s: 1.8.8
> Log hex dump of too big segme
[
https://issues.apache.org/jira/browse/OAK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598707#comment-16598707
]
Francesco Mari commented on OAK-7720:
-
Backported to 1.8 at r1839758.
> Log hex dump of too
I intend to backport OAK-7720 to the 1.8 and 1.6 branch. The fix makes the
system log a dump of too big segments to ease debugging the corruption of
the segment buffer.
[
https://issues.apache.org/jira/browse/OAK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7720.
-
Resolution: Fixed
Fix Version/s: 1.9.9
Fixed at r1839746.
> Log hex dump of too
[
https://issues.apache.org/jira/browse/OAK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7720:
Fix Version/s: 1.10
> Log hex dump of too big segme
[
https://issues.apache.org/jira/browse/OAK-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598452#comment-16598452
]
Francesco Mari commented on OAK-7724:
-
[~amitjain], I think that the condition coincides
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598442#comment-16598442
]
Francesco Mari commented on OAK-7721:
-
[~mduerig], in the second version of the patch the test fails
[
https://issues.apache.org/jira/browse/OAK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated OAK-7721:
Attachment: OAK-7721-02.patch
> Records of specific size bring SegmentBufferWriter#flush to f
301 - 400 of 4475 matches
Mail list logo
