Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix resulting buffer from BufferProxy's out method being ignored.#255

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
LambdAurora wants to merge2 commits intolmdbjava:master
base:master
Choose a base branch
Loading
fromLambdAurora:fix/bufferproxy_out_ignored

Conversation

LambdAurora
Copy link

This pull request aims to fix some cases in LMDBJava where theBufferProxy'sout method resulting buffer is ignored, especially inDbi.

I've discovered this issue while attempting to write a new implementation ofBufferProxy to use Java 22's Function Foreign Memory API in preparation of Java 25's removal of various methods inUnsafe invalidating most fastBufferProxy implementations. The implementation failed to pass some tests since in theout method I returned a newByteBuffer (taking advantage ofMemorySegment.ofAddress().asByteBuffer()).

After further investigation, I've found thatByteArrayProxy also relies on returning a different "buffer" from the one that's given as an argument, for which I've added new tests that reproduce the behavior ofDbiTest.customComparator andDbiTest.dbiWithComparatorThreadSafety using byte arrays instead.ByteArrayProxy led me to think that returning a different buffer inout is an allowed and intended behavior.

This fix is important for users ofByteArrayProxy and allows for a stop-gap external implementation ofBufferProxy using the FFM API to allow users to upgrade to Java 25 when the time comes until a proper resolution to#42 comes around.

TODO: address failing dbiWithComparatorThreadSafetyByteArray test.
This proves to be more reliable than Agreno's UnsafeBuffers.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

1 participant
@LambdAurora

[8]ページ先頭

©2009-2025 Movatter.jp