让消费函数返回底层的错误原因

Author: yangyile

rabbitmq/consume.go

@@ -20,6 +20,7 @@ func ConsumeMessage(ctx context.Context, cfg *Config, handleFunc HandleFunc, max
 	var onceLimit sync.Once
 	var waitGroup sync.WaitGroup
 	var outReason ReasonType
+	var outErrors error
 	waitGroup.Add(1) //在线程内部的某处会完成它
 	go func() {
 		for {
@@ -29,6 +30,7 @@ func ConsumeMessage(ctx context.Context, cfg *Config, handleFunc HandleFunc, max
 				//假如已经成功初始化，这里就进不来，而只要能进来就必然是未初始化的
 				onceLimit.Do(func() {
 					outReason = must.Sane(reason, MqCannotInit)
+					outErrors = err
 					waitGroup.Done()
 				})
 				//假如首次连接就失败，就不重试连接，因为首次错误往往是配置问题，需要把错误返回给上层让他们选择
@@ -56,17 +58,19 @@ func ConsumeMessage(ctx context.Context, cfg *Config, handleFunc HandleFunc, max
 	waitGroup.Wait() //前面是 go routine，但首次初始化还是要确认它能成功，因此这里会等待确认第一次连接成功
 	log.DebugLog("rabbit-mq-init-success", zap.String("queue_name", cfg.QueueName))
 	if outReason == MqCannotInit {
-		return erero.New(string(MqCannotInit))
+		must.True(outErrors != nil)
+		return erero.WithMessage(outErrors, string(MqCannotInit))
 	}
 	must.Zero(outReason)
+	must.Done(outErrors)
 	return nil
 }
 
 type ReasonType string
 
 const (
 	ContextIsDone  ReasonType = "context-is-done"
-	MqCannotInit   ReasonType = "mq-cannot-init"
+	MqCannotInit   ReasonType = "mq-can-not-init"
 	MqDisconnected ReasonType = "mq-disconnected"
 )