Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Service Arch 2022-05-30
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

ThreadContext is no longer required for ThreadName after ~~SERVER-66385~~.
The rather indirect fix for ~~SERVER-58194~~ is likely unnecessary now and the destructor code for OpMsgFuzzerFixture can return to its original condition.

depends on

SERVER-66385 Remove ThreadName's dependence on ThreadContext (& vice versa apparently)

Closed

is related to

SERVER-58194 Fix undefined behavior in the destructor for OpMsgFuzzerFixture

Closed

Assignee:: Billy Donahue
Reporter:: Billy Donahue
Participants:: Billy Donahue, Githook User
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: May 13 2022 05:58:25 AM UTC
Updated:: Oct 29 2023 09:38:16 PM UTC
Resolved:: May 16 2022 03:38:06 PM UTC
Confidence Status Last Update:: 13/May/22 9:44 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates