[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: |
|
||||
| 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 |