Questions about go fmt

[xianjingfeng]

When i exec build-operator.sh, the follow logs was printed:

image version release.0.4.0.453.g567872b8.dirty is dirty, dirty files:

And then i found some files(https://github.com/apache/incubator-uniffle/pull/759/files) was formatted.

But i found it seems ok in current code base.

My questions is as follows:

1. Why is the result of go fmt in local development environment different from the ci environment?
2. Whether it is necessary to judge whether the file is dirty when executing build-operator.sh? It's inconvenient because sometimes we need do some test before commit.

[xianjingfeng]

@wangao1236 Cound you answer?

[DeedeeOlesonFnt]

Just a little opinion, I hope it can help you
The difference in the result of go fmt between local development environment and CI environment could be due to differences in the versions of Go and/or Go packages being used. It's also possible that there are different configurations between the two environments that affect the output of go fmt.

[xianjingfeng]

Thanks for your answer. Do you have an idea to ensure that the developer environment is consistent with the cienvironment?

[sheltonjynk]

The result of go fmt may differ in local and CI environments due to differences in the Go version and environment variables. It is not necessary to check for dirty files before running build-operator.sh, but it is a good practice to ensure that the code being built is clean and consistent.