-
Notifications
You must be signed in to change notification settings - Fork 10k
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
fix!: LDAP sync triggers multiple cron jobs in case an invalid sync interval is provided #32285
base: release-7.0.0
Are you sure you want to change the base?
fix!: LDAP sync triggers multiple cron jobs in case an invalid sync interval is provided #32285
Conversation
Co-authored-by: Diego Sampaio <chinello@gmail.com>
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: fe1a4c1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 34 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.0.0 #32285 +/- ##
=================================================
- Coverage 55.59% 55.53% -0.06%
=================================================
Files 2427 2410 -17
Lines 53337 53074 -263
Branches 10970 10909 -61
=================================================
- Hits 29651 29475 -176
+ Misses 21050 20979 -71
+ Partials 2636 2620 -16
Flags with carried forward coverage won't be shown. Click here to find out more. |
Co-authored-by: Diego Sampaio <chinello@gmail.com>
Co-authored-by: Diego Sampaio <chinello@gmail.com>
The merge-base changed after approval.
Co-authored-by: Diego Sampaio <chinello@gmail.com>
* chore: Improve permission check on channels endpoints
Co-authored-by: Marcos Spessatto Defendi <marcos.defendi@rocket.chat>
…Chat into fix/ldap-triggers-multiple-cron-jobs
Proposed changes (including videos or screenshots)
packageValue
s as the fallback value in case the provided value is invalid;packageValue
s (from cron description to actual cron expressions, which is the type of value expected by RC since 6.3).Issue(s)
Steps to test or reproduce
Go to Settings > LDAP > Premium and set an invalid Avatar Background Sync Interval or Auto Logout Interval.
Current behavior: cron jobs are triggered successively (there is no interval between them).
Expected behavior: cron jobs intervals should follow each setting's default value instead.
Further comments
CORE-273