[SERVER-78292] Issue with Object.entries in mongotmock assertEmpty Created: 21/Jun/23  Updated: 29/Oct/23  Resolved: 26/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc6, 6.0.8

Type: Bug Priority: Major - P3
Reporter: Militsa Sotirova Assignee: Militsa Sotirova
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0, v6.0
Steps To Reproduce:

Change the usage of Object.entries in mongotmock's assertEmpty to instead be a for...in and search_batchsize.js fails.

Sprint: QO 2023-06-26, QO 2023-07-10
Participants:

 Description   

See SERVER-78357 for a detailed explanation of why. Replace the usage of Object.entries with for...in. Also fix the jstests that are mocking extra responses.


Generated at Thu Feb 08 06:37:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.