Revert adding PerfdataWriterConnection#10851
Merged
Merged
Conversation
bb821da to
103779d
Compare
Member
|
I've checked using
|
julianbrost
previously approved these changes
May 20, 2026
Contributor
Author
The only real exception I made outside of solving those conflicts was also keeping the |
This was referenced May 20, 2026
103779d to
cef29ed
Compare
cef29ed to
9110c45
Compare
Contributor
Author
|
julianbrost
approved these changes
May 20, 2026
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
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.
We still can't reproduce #10825 on our end or get any reliable info on what is causing the problem, so this reverts the merges of #10799 and #10668 on the 2.16 branch.
We are aware of #10848 and the locking issue discovered there, but for now concluded that rolling out a fix for that is too uncertain, without knowing the underlying issue of why the perfdata writer queues stop.
refs #10842 (this PR fixes it for support/2.16, issue remains open for master branch)
refs #10848 (this PR fixes it for support/2.16, issue remains open for master branch)
refs #10825 (this PR fixes it for support/2.16, issue remains open for master branch)