使用errors.Wrapf()代替log.Error()

介绍不同语言的错误处理机制: Error handling patterns

Musings about error handling mechanisms in programming languages

项目中 main调func1,func1调取func2...

这样就会出现很多的 if err != nil { log.Printf()} , 在Kibana上查看时会搜到多条日志, 需要逐级定位, 确定错误抛出的点

希望只有一条, 能清晰看到整个堆栈调用信息

使用log.xxxx方法:

go 复制代码
package main

import (
	"fmt"
	"log"
	"strconv"
	"time"
)

func init() {
	log.SetFlags(log.Lshortfile | log.LstdFlags)
}

func main() {

	str := "123a"
	rs, err := func1(str)

	if err != nil {
		log.Printf("err is (%+v)\n", err)
		return
	}

	fmt.Println("最终结果为:", rs)

}

func func1(str string) (int, error) {

	b, err := func2()

	if err != nil {
		log.Printf("There is func11111,  func2 err(%+v)\n", err)
	}

	if b == false {
		strInt, err := strconv.Atoi(str)

		if err != nil {
			log.Printf("There is func11111, err(%+v)\n", err)
		}
		return strInt, err
	}
	return 0, nil
}

func func2() (bool, error) {

	now := time.Now().Unix()

	endTimeStr := "2021-08-06 20:00:0000"

	endtime, err := time.ParseInLocation("2006-01-02 15:04:05", endTimeStr, time.Local)

	if err != nil {
		log.Printf("There is func22222, err(%+v)\n", err)
		return false, err
	}

	if endtime.Unix() > now {
		return true, nil
	}

	return false, nil

}

执行结果:

go 复制代码
2021/06/07 21:52:56 vs.go:56: There is func22222, err(parsing time "2021-08-06 20:00:0000": extra text: "00")
2021/06/07 21:52:56 vs.go:33: There is func11111,  func2 err(parsing time "2021-08-06 20:00:0000": extra text: "00")
2021/06/07 21:52:56 vs.go:40: There is func11111, err(strconv.Atoi: parsing "123a": invalid syntax)
2021/06/07 21:52:56 vs.go:20: err is (strconv.Atoi: parsing "123a": invalid syntax)

使用errors.Wrapf方法:

go 复制代码
package main

import (
	"fmt"
	"github.com/pkg/errors"
	"strconv"
	"time"
)

func main() {

	str := "123a"
	rs, err := func1(str)

	if err != nil {

		fmt.Printf("err: %+v\n", err)
		//fmt.Println("err:", lastErr) //必须%+v才会打印完整堆栈信息,否则只打印错误信息
		return
	}

	fmt.Println("最终结果为:", rs)

}

func func1(str string) (int, error) {

	b, err := func2()

	if err != nil {
		err = errors.Wrapf(err, "There is func11111, func2 err, b is(%b) \n", b)
	}

	if b == false {
		var strInt int
		strInt, err = strconv.Atoi(str)

		if err != nil {
			err = errors.Wrapf(err, "There is func11111,str is(%s)\n", str)
		}
		return strInt, err
	}
	return 0, nil
}

func func2() (bool, error) {

	now := time.Now().Unix()

	endTimeStr := "2021-08-06 20:00:0000"

	endtime, err := time.ParseInLocation("2006-01-02 15:04:05", endTimeStr, time.Local)

	if err != nil {
		err = errors.Wrapf(err, "There is func22222,endTimeStr is(%s)\n", endTimeStr)
		return false, err
	}

	if endtime.Unix() > now {
		return true, nil
	}

	return false, nil

}

执行:

go 复制代码
err: strconv.Atoi: parsing "123a": invalid syntax
There is func11111,str is(123a)

main.func1
        /Users/fliter/go/src/shuang/llog/1.go:39
main.main
        /Users/fliter/go/src/shuang/llog/1.go:13
runtime.main
        /usr/local/Cellar/go/1.16.3/libexec/src/runtime/proc.go:225
runtime.goexit
        /usr/local/Cellar/go/1.16.3/libexec/src/runtime/asm_amd64.s:1371

注意赋值这步, 必不可少!

有一个问题, 即对于f1调f2,f2调f3这种, 如果f3发生error, 可以逐级将error抛出.

但如果一个方法里有两个error, 则第二条会覆盖掉第一条,如上 err = errors.Wrapf(err, "There is func11111, func2 err, b is(%b) \n", b)这一条就被覆盖了

go 复制代码
// Wrapf returns an error annotating err with a stack trace
// at the point Wrapf is called, and the format specifier.
// If err is nil, Wrapf returns nil.
func Wrapf(err error, format string, args ...interface{}) error {
	if err == nil {
		return nil
	}
	err = &withMessage{
		cause: err,
		msg:   fmt.Sprintf(format, args...),
	}
	return &withStack{
		err,
		callers(),
	}
}
go 复制代码
func callers() *stack {
	const depth = 32
	var pcs [depth]uintptr
	n := runtime.Callers(3, pcs[:])
	var st stack = pcs[0:n]
	return &st
}
go 复制代码
// Callers fills the slice pc with the return program counters of function invocations
// on the calling goroutine's stack. The argument skip is the number of stack frames
// to skip before recording in pc, with 0 identifying the frame for Callers itself and
// 1 identifying the caller of Callers.
// It returns the number of entries written to pc.
//
// To translate these PCs into symbolic information such as function
// names and line numbers, use CallersFrames. CallersFrames accounts
// for inlined functions and adjusts the return program counters into
// call program counters. Iterating over the returned slice of PCs
// directly is discouraged, as is using FuncForPC on any of the
// returned PCs, since these cannot account for inlining or return
// program counter adjustment.
func Callers(skip int, pc []uintptr) int {
	// runtime.callers uses pc.array==nil as a signal
	// to print a stack trace. Pick off 0-length pc here
	// so that we don't let a nil pc slice get to it.
	if len(pc) == 0 {
		return 0
	}
	return callers(skip, pc)
}
go 复制代码
func callers(skip int, pcbuf []uintptr) int {
	sp := getcallersp()
	pc := getcallerpc()
	gp := getg()
	var n int
	systemstack(func() {
		n = gentraceback(pc, sp, 0, gp, skip, &pcbuf[0], len(pcbuf), nil, nil, 0)
	})
	return n
}

参考:

golang 打印error的堆栈信息

Go错误处理最佳实践

相关推荐
ServBay29 分钟前
Local harness 将退役,VS Code 本地开发要不要搬到云端?
后端·ai编程·visual studio code
ashiho1 小时前
【LeetCode hot 100】3. 无重复字符的最长子串 (三种解法)
java·数据结构·后端·算法·leetcode·滑动窗口
张一凡932 小时前
你的 AGENTS.md,真的管到模型写代码了吗?
前端·后端·agent
00后程序员2 小时前
iOS 实时活动怎么开发,Windows 上用 KXBuild 和 ActivityKit 写灵动岛
后端·ios
程序员cxuan2 小时前
推荐 10 个 WorkBuddy 中的邪修用法
人工智能·后端·程序员
Bacon2 小时前
给项目做一次"全身 CT":Agent Skills 生态里的代码体检全链路
前端·人工智能·后端
Java旅途3 小时前
课程表编排与调课申请系统|排得开,也能把每次调整管清楚
后端
象牙塔五六七3 小时前
Java 泛型精讲:从 Stream 源码说起
后端
掘金挖土3 小时前
前端手摸手跑路之 AI 应用开发(十二)
前端·后端
程序员cxuan3 小时前
GPT-6.2 Astra 发布了,但口碑崩了。。。
人工智能·后端·程序员