- log msg refactor, add orderID to all logs.

legacy/elm/controller/order.go

@@ -80,7 +80,6 @@ func (o *OrderController) NewOrder(msg *elmapi.CallbackMsg, orderId string, user
 		retVal = errResponseDBError
 	} else {
 		if created || rec.Type < msg.Type {
-			// todo 回调消息里已经有详情，这里是否有必要再取一次？
 			result, err := api.ElmAPI.GetOrder(orderId)
 			if err != nil {
 				retVal = errResponseCallELMAPIError

legacy/freshfood/freshfood.go

@@ -133,11 +133,11 @@ func (f *API) AccessFreshFood(apiStr string, params url.Values) error {
 		if err == nil && response != nil && response.StatusCode == 200 {
 			break
 		} else {
-			globals.SugarLogger.Infof("Call %s error:%v, response: %v", fullURL, err, response)
+			globals.SugarLogger.Infof("AccessFreshFood Call %s error:%v, response: %v", fullURL, err, response)
 		}
 	}
 	if err != nil || response.StatusCode != 200 {
-		globals.SugarLogger.Errorf("Call %s error:%v, url:%s, response: %v", fullURL, err, fullURL, response)
+		globals.SugarLogger.Errorf("AccessFreshFood Call %s error:%v, url:%s, response: %v", fullURL, err, fullURL, response)
 		if err != nil {
 			return err
 		}

legacy/jd/controller/order.go

@@ -28,7 +28,6 @@ func InitOrder() {
 	orderMsgChan = make(chan jdapi.CallbackOrderMsg, 128)
 	go orderMsgHandlerRoutine()
 
-	// todo 这样操作在有多个进程时，会有问题
 	// 另外当前这个模式可能会出现同一个订单的消息，虽然远程推送过来顺序是对的，但经过处理后推送到freshfood时乱序（因为每个消息的处理时间是不确定的）
 	handlePendingOrderMsg()
 }
@@ -161,7 +160,6 @@ func newOrder(msg *jdapi.CallbackOrderMsg) error {
 		rec.Msg, _ = result["msg"].(string)
 		rec.Success, _ = result["success"].(bool)
 
-		// todo
 		rec.CityName = "all"
 
 		data := result["data"].(map[string]interface{})