su chen

Emmm, I think there are several cases we should consider carefully: 1. if `beforePipeline` failed, it is `end`, `pipeline`, `afterPipeline` three case. 2. if `pipeline` failed, it is `end`, `afterPipeline`...

And i am also afraid that add an option to pipeline spec works fine for a small set of pipelines. Some of our user may use 1000 pipelines. Then if...

By the way, sorry for the delay.

Hi, @chenrui333 could you please fix it? We'd like to update easeprobe to golang 1.21.

we are now in go 1.21, so i will close this pr.

It seems in this pr https://github.com/megaease/easeprobe/pull/386/files#diff-f4ba94b6ceb9d73b8797e5ca558f756010112d0d6b71ca4ffcdf3da10fbe2c1f, the author add constant labels and change `LatChainExpiryTimestampSeconds` to `EarliestExpiry` by mistake, as a result there are two `EarliestExpiry`? If you change it back,...

This problem has existed for a long time, and it's unfortunate that `bou.ke/monkey` does not work on Mac M1. If `gomonkey` works on all chips and offers all the functionality...

Well, I thought you were using a Mac M1... If it doesn’t affect your work, I would prefer the second option. Could we also add another `build.yaml` to the GitHub...