Ticket #48046

"obsinv" client connected to older server still suffers from the assert

Open Date: 2023-05-14 14:50 Last Update: 2023-06-07 16:09

Reporter:
Owner:
Type:
Status:
Closed
Component:
MileStone:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
1

Details

In S3_1, S3_0, and S2_6, #46186 fixes an assert using an optional network capability. This still leave the assert failing on a new client connecting to an older server. It should not treat the situation as a client code bug (to assert against), but known failure on those older servers.

Newer branches are not affected, as there's no optional capability -> no compatible servers with the bug present.

Ticket History (3/5 Histories)

2023-05-14 14:50 Updated by: cazfi
  • New Ticket ""obsinv" client connected to older server still suffers from the assert" created
2023-05-14 15:04 Updated by: cazfi
  • Details Updated
2023-06-01 22:31 Updated by: cazfi
  • Owner Update from (None) to cazfi
  • Resolution Update from None to Accepted
Comment

Reply To cazfi

In S3_1, S3_0, and S2_6

Patch for those affected branches attached.

2023-06-07 16:09 Updated by: cazfi
  • Status Update from Open to Closed
  • Resolution Update from Accepted to Fixed

Edit

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Login