-
-
Notifications
You must be signed in to change notification settings - Fork 55
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the cache configurable by cpp API #950
Conversation
433e1b4
to
6c5f25e
Compare
CI seems to be broken for other reasons than this PR. |
6c5f25e
to
2c34dbf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's have #949 merged first. I will review the rebased&fixed-up version of this PR again after conflict resolution.
2c34dbf
to
e6fbbbf
Compare
PR is now rebased&fixed-up and conflict are resolved. |
fe9ee9d
to
4a1881a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All my feedback was restricted to the test code, which means that generally the PR is good to merge.
4a1881a
to
117868f
Compare
Last push updates with your comments. Only |
55616af
to
f3ea99f
Compare
I have added a small comment about no reset the |
f3ea99f
to
cc02757
Compare
cc02757
to
c853517
Compare
This (almost) last push rename all introduced method from snake_case to camelCase as this is our coding style. fixup commits are interleaved in the git history. @veloman-yunkan please give a formal approval before I rebase-fixup (and reword commit messages) and merge without further approval. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only checked the full diff from the previous version without inspecting each fixup commit separately. LGTM.
- DirentLookup becoming polymorphic - Possibility to disable lookup caching altogether - Once created, this cache size cannot be modified
Probably nobody never set this, and we don't use lzma anymore.
We don't use it anymore.
This make fail the test as it appears we create the dirent lookup cache at initialization. This will be fixed in next commits.
There is no reason this setting is done while reading the mimetype.
Let's use a temp dirent lookup (without cache) to access titleOrdered v1 and 'C' namespace.
Reading and writing in the same time to a unique_ptr is not thread safe. We introduce a atomicBool to know if the unique_ptr has been initialized. Fix #945
c853517
to
8dd1508
Compare
This fix #946.
Contrary to what proposed in #946, this doesn't introduce a cache config structure but use simple method:
This PR probably have some small conflict with #949, I will resolve them as soon as a PR is merged.