docs(readme): Add warning about breakage on Linux >=6.19#267
Closed
flexxyfluxx wants to merge 2 commits intostoatchat:mainfrom
Closed
docs(readme): Add warning about breakage on Linux >=6.19#267flexxyfluxx wants to merge 2 commits intostoatchat:mainfrom
flexxyfluxx wants to merge 2 commits intostoatchat:mainfrom
Conversation
Signed-off-by: flexxyfluxx <82163962+flexxyfluxx@users.noreply.github.com>
Signed-off-by: flexxyfluxx <82163962+flexxyfluxx@users.noreply.github.com>
Member
|
Thank you for your contribution. I think due to the temporary nature of this, it should be a git issue that references the mongo issue instead. Could you open a git issue for this problem? |
Author
|
Will do. Closing. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See https://www.mongodb.com/docs/manual/release-notes/8.0/
It may be that Kernel versions as early as 6.17 may also be affected (see google/tcmalloc#292; possibly even 6.6), but the official mongodb notice references 6.19 as the first broken version, so that's what I went with.
Open to slimming the notice down a little.
I'm on the fence about the utility of the second line of the notice. Rationale behind adding it was that it may help users encountering this issue figure out faster that their issue is related to this breakage, and thus spare at least a few people some of the frustration.