Release 3.7.1 #19189
Merged
Release 3.7.1 #19189
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
Co-authored-by: Diego Sampaio <chinello@gmail.com>
rodrigok
approved these changes
Oct 9, 2020
|
this bug is still here in 3.9.4 |
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.
2020-10-09 · 6 🐛 · 5 👩💻👨💻Engine versions
12.18.46.14.83.4, 3.6, 4.01.18.0🐛 Bug fixes
Adding missing custom fields translation in my account's profile (#19179)
Admin Sidebar overflowing (#19101)
Missing "Bio" in user's profile view ("Bio" field doesn't appear when viewing a user's profile #18821) (#19166)
Omnichannel: triggers page not rendering. (#19134)
Performance issues when using new Oplog implementation (#19181)
A missing configuration was not limiting the new oplog tailing to pool the database frequently even when no data was available, leading to both node and mongodb process been consuming high CPU even with low usage. This case was happening for installations using
mmapv1database engine or when no admin access was granted to the database user, both preventing the usage of the new Change Streams implementation and fallbacking to our custom oplog implementation in replacement to the Meteor's one what was able to be disabled and use the native implementation via the environmental variableUSE_NATIVE_OPLOG=true.VisitorAutoComplete component (#19133)
👩💻👨💻 Core Team 🤓