Daniel Iwan

I resolved some of the conversations I agreed with I haven't check in the code yet however as others needs some clarifications Is that the way to do it? Do...

Hi Hakky54 Thanks for prompt reply. Using just `withUnsafeTrustMaterial` indeed fixes the problem since `CombinableX509TrustManager` is no longer used. As for the reasons why I used both `withDefaultTrustMaterial` and `withUnsafeTrustMaterial`...

Hi I reverted my code changes and tested with 7.4.5 and it works as expected. Thanks for you quick response. I have one question regarding the changes for this patch,...

HI Sorry for late reply I gave it a go but unfortunately it breaks several tests which rely on the existing behaviour. For example it is common in the test...

Created here https://github.com/Hakky54/sslcontext-kickstart/pull/204 Hopefully i've done it right. I'm not sure if there is automatic way to link pull request with Github issue?

At the moment this is the only thing that prevents me from using MarkText. Opening a document to edit small part (spelling mistake) causes many changes. Particularly bad for tables,...

Just confirmed that dropping commit 3524995b97c86e0cd66c64ce648693cad9feaa0c brings back previous behaviour and my test pass. In case it's relevant when I'm opening database I do ``` Dbi db = _env.openDbi(hexId, MDB_CREATE);...

Further tests show that if I open db like this ``` Comparator cmp = new MyComparatorCopiedFromByteBufferProxy(); Dbi db = _env.openDbi(hexId, cmp, MDB_CREATE); ``` where `MyComparatorCopiedFromByteBufferProxy` has implementation copied from `org.lmdbjava.ByteBufferProxy$AbstractByteBufferProxy`...

It looks like the problem is related to changing what is a default comparator for ByteBuffer. In pre 0.9.0 it was a custom lmdbjava implementation which was doing unsigned comparison....

Hi No, it was not working, see my comment >> Supplying MDB_INTEGERKEY also does not work, not clear to me why On Mon, 5 Feb 2024 at 06:21, Cosimo Damiano...