[SERVER-18157] Coverity analysis defect 72637: Inferred misuse of enum Created: 21/Apr/15  Updated: 19/Sep/15  Resolved: 03/Jun/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.1.4

Type: Bug Priority: Major - P3
Reporter: Coverity Collector User Assignee: Daniel Alabi
Resolution: Done Votes: 0
Labels: coverity
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

A new defect has been detected and assigned to daniel.alabi@10gen.com in Coverity Connect.
http://coverity.mongodb.com//sourcebrowser.htm?projectId=10001#mergedDefectId=72637
The defect was flagged by checker MIXED_ENUMS in
file /src/mongo/s/d_migrate.cpp
function mongo::MoveChunkCommand::run(mongo::OperationContext *, const std::basic_string<char, std::char_traits<char>, std::allocator<char>>&, mongo::BSONObj &, int, std::basic_string<char, std::char_traits<char>, std::allocator<char>>&, mongo::BSONObjBuilder &)
and this ticket was created by amalia.hawkins@10gen.com



 Comments   
Comment by Githook User [ 03/Jun/15 ]

Author:

{u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}

Message: SERVER-18157 Appropriately handle applyOps status during migration
Branch: master
https://github.com/mongodb/mongo/commit/7c1e8a0f74f62fca4e2e636de8f0752a111ded72

Generated at Thu Feb 08 03:46:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.