Fix access check in time tracking controller #7055
Merged
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
frcroth
approved these changes
May 8, 2023
philippotto
pushed a commit
that referenced
this pull request
May 8, 2023
philippotto
added a commit
that referenced
this pull request
May 8, 2023
* Release 23.05.0 * Guard against NaNs in shader (#7018) * guard against nan when deciding whether to use performance optimization in shader * update changelog * Workaround for WebGL crash for datasets with many segmentation layers (#6995) * reduce shader complexity when having multiple segmentation layers (shader needs to be compiled more often then, though) * fix tests * clean up * update changelog * Release 23.05.1 * Fix access check in time tracking controller (#7055) * Release 23.05.2 --------- Co-authored-by: Florian M <fm3@users.noreply.github.com>
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.
Not the full user object should be compared for the access check, that created false differences in lastActivity timestamp. (User caching recently changed slightly, but this should not be able to have effects here)
Steps to test: