-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Closed
Labels
Servicing-approvedShiproom has approved the issueShiproom has approved the issuearea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
Milestone
Description
Description
In 5.0 some logging updates were made that accidentally swapped the argument parameters for a log.
Customer Impact
Customers consuming structured logging might depend on the types of the structured data, swapping the arguments can break them as seen above, also the log reads incorrectly.
Regression?
- Yes
- No
Regressed from 3.1 to 5.0 (fixed in 6.0 already)
Risk
- High
- Medium
- Low
The change is a logging change only, just switching the parameter order.
Verification
- Manual (required)
- Automated
Packaging changes reviewed?
- Yes
- No
- N/A
Hi!
It is possible to merge fix from #28698 to branch 5.*?
Best regards,
Mateusz
Metadata
Metadata
Assignees
Labels
Servicing-approvedShiproom has approved the issueShiproom has approved the issuearea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions