-
Notifications
You must be signed in to change notification settings - Fork 6
[NAE-2288] Delete of process retains global role from user #390
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
Open
renczesstefan
wants to merge
4
commits into
release/7.0.0-rev9
Choose a base branch
from
NAE-2288
base: release/7.0.0-rev9
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+22
−13
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3a6ab12
[NAE-2288] Delete of process retains global role from user
renczesstefan ba05893
Improve null handling, performance, and serialization
renczesstefan f05b60e
[NAE-2288] Delete of process retains global role from user
renczesstefan 39b5a8f
- removed commented code
renczesstefan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Critical pagination bugs cause infinite loop and data corruption.
The realm-aware pagination implementation has two critical issues:
Infinite loop:
realmPageableis never incremented, so line 558 fetches the same realm page indefinitely whenrealms.hasNext()is true.User pagination not reset:
pageableis declared at line 552 and incremented at line 564, but never reset between realms. This causes users in the second and subsequent realms to be skipped. For example, if Realm 1 has 3 pages of users, Realm 2 will start at page 3, missing pages 0-2.Apply this diff to fix both issues:
public void removeRoleOfDeletedPetriNet(Set<ProcessRole> petriNetRoles) { - Pageable pageable = PageRequest.of(0, paginationProperties.getBackendPageSize()); Set<ProcessRole> nonGlobalPetriNetRoles = petriNetRoles.stream().filter(r -> !r.isGlobal()).collect(Collectors.toSet()); Collection<ProcessResourceId> roleIds = nonGlobalPetriNetRoles.stream().map(ProcessRole::get_id).collect(Collectors.toSet()); Pageable realmPageable = PageRequest.of(0, paginationProperties.getBackendPageSize()); Page<Realm> realms; do { realms = realmService.getSmallRealm(realmPageable); Page<AbstractUser> users; for (Realm realm : realms.getContent()) { + Pageable pageable = PageRequest.of(0, paginationProperties.getBackendPageSize()); do { users = searchUsersByRoleIds(roleIds, collectionNameProvider.getCollectionNameForRealm(realm.getName()), pageable); users.getContent().forEach(u -> removeRoles(u, nonGlobalPetriNetRoles)); pageable = pageable.next(); } while (users.hasNext()); } + realmPageable = realmPageable.next(); } while (realms.hasNext()); }🤖 Prompt for AI Agents
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.
Very good comment. I find both issues relevant. Please fix it and I think this refactor needs better attention to testing
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.
@Retoocs, thank you for confirming! Here's the complete fixed method:
Key changes:
pageablenow initialized inside the realm loop, ensuring each realm starts from page 0realmPageablenow incremented after processing each realm pageTesting recommendations:
Given the complexity of multi-realm pagination, I strongly recommend adding integration tests that cover:
Would you like me to help generate unit test scaffolding for these scenarios?
🧠 Learnings used