feat: caching user single id in preferences #2108
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ArtificialOwl
force-pushed
the
feat/noid/cache-user-single-id
branch
5 times, most recently
from
2086211 to
6fba05a
Compare
ArtificialOwl
force-pushed
the
feat/noid/cache-user-single-id
branch
2 times, most recently
from
d67506b to
d5e8a07
Compare
Signed-off-by: Maxence Lange <[email protected]>
ArtificialOwl
force-pushed
the
feat/noid/cache-user-single-id
branch
from
d5e8a07 to
8de3a62
Compare
provokateurin
approved these changes
Sep 28, 2025
Member
Author
|
/backport to stable32 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
it has been reported that the current way of storing local user single id does not scale on huge setup.
because the value is not supposed to change, it is now stored in
preferences.