[SERVER-24965] Change resync.js to expect UnknownError instead of CappedPositionLost on the 3.0 branch Created: 08/Jul/16  Updated: 01/Nov/16  Resolved: 14/Jul/16

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.0.13

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-24559 UnknownError can be returned on PlanE... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 17 (07/15/16)
Participants:
Linked BF Score: 0

 Description   

This is done to work around the issue described in SERVER-24559.



 Comments   
Comment by Githook User [ 14/Jul/16 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-24965 Change test to expect UnknownError if collection truncated.

We'd normally expect CappedPositionLost in this scenario, but a bug in
the 3.0 branch prevents the status member object from being propagated
back to the client.
Branch: v3.0
https://github.com/mongodb/mongo/commit/f070dd1fe27fa811778348475044cb1f14b3f0ef

Generated at Thu Feb 08 04:07:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.