fix: delete wrong cached type #7813
Closed
Conversation
This file contains 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
vitoreiji
approved these changes
Oct 24, 2024
juni2k
force-pushed
the
crypto/fix-1883
branch
from
20465c2
to
26801e0
Compare
vitoreiji
force-pushed
the
crypto/fix-1883
branch
2 times, most recently
from
e90a3ee
to
4824fd7
Compare
If there was a password change, the old session is deleted later in the log in process, causing the user to get logged out. Co-authored-by: bedhub <bedhub@users.noreply.github.com> tutadb#1897
There was a mismatch in the type asking to be removed from the cache This cause the client to throw when the admin was logging in tutadb#1883
vitoreiji
force-pushed
the
crypto/fix-1883
branch
from
4824fd7
to
b775cfa
Compare
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.
When asking to remove a cached type, there is a mismatch between the type asking to be removed and the one in the cache. This causes the client to throw when the admin was logging in
tutadb#1883