Closed darix closed 4 months ago
I can reproduce this. :heavy_check_mark: Since this implies non-backwards-compatible behavior of the Go compiler, isn't this rather an issue for the Go project?
I just wanted to make the project aware that there is an issue.
This issue is a blocker for me, I can't move to go 1.22 if the mockery panics and I understand it can be an issue that may be fixed in go 1.22.1 but someone must open an issue on google side
Posted a fix.
It's a bit of a blocker for us, we're using mockery without installing it in CI, via go run
, so it gets coupled with the compiler version that CI uses. It's a convenient way for us to pin mockery version across dev machines and CI without relying on dockerized execution.
//go:generate go run github.com/vektra/mockery/v2@v2.40.1
I can confirm that @viktorasm fix worked for me
Fixed in mockery v2@2.40.2 (https://github.com/vektra/mockery/releases/tag/v2.40.2) specifically https://github.com/vektra/mockery/commit/f513d5d71a384ba7b0c46e8731321c0fada7881f
Description
Mockery Version
2.40.1
Golang Version
1.22rc2 works with 1.21
Installation Method
Steps to Reproduce
Expected Behavior
not crashing
Actual Behavior
crashing