-
Notifications
You must be signed in to change notification settings - Fork 13.7k
fix: use $ne operator in findCustomRoles to prevent false negatives #41031
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
aegisforensicsmonk
wants to merge
4
commits into
RocketChat:develop
Choose a base branch
from
aegisforensicsmonk:fix/findCustomRoles-false-negative
base: develop
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.
+8
−2
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f6f8608
fix: use $ne operator in findCustomRoles to prevent false negatives
aegisforensicsmonk 7db02e6
fix: ensure protected flag is set for built-in roles during startup
aegisforensicsmonk 1ffba51
Merge branch 'develop' into fix/findCustomRoles-false-negative
aegisforensicsmonk 58dbc6c
chore: address review feedback for protected roles fix
aegisforensicsmonk 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| --- | ||
| '@rocket.chat/models': patch | ||
| '@rocket.chat/meteor': patch | ||
| --- | ||
|
|
||
| Fix custom roles not being found when `protected` is missing. Closes #40798. |
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
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.
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.
On upgraded workspaces where default roles were created before
protectedexisted, those roles can still be missing the field: startup runscreateOrUpdateProtectedRoleAsync, but its existing-role path only callsRoles.updateById(...)and never writesprotected: true. This predicate therefore makes built-in roles likeadmin,moderator, andusermatchfindCustomRoles/countCustomRoles, so Apps-Engine custom-role reads and custom-role statistics include protected default roles instead of only real custom roles. The fix should distinguish known protected roles or migrate/default theirprotectedflag, rather than treating every missing value as custom.Useful? React with 👍 / 👎.
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.
Thanks for pointing this out. My intention was to include custom roles where the
protectedfield is missing, since the previous query only matched roles withprotected: false.However, I see the issue with legacy workspaces where built-in roles such as
admin,moderator, andusermay also be missing theprotectedfield. In those cases, usingprotected: { $ne: true }would incorrectly classify those default roles as custom roles.I'll revisit the approach and look into a solution that correctly handles legacy protected roles, either by ensuring their
protectedflag is properly set through a migration or by explicitly distinguishing them from custom roles.