You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically, the package is server/util/db with a single source file db.go. The upgraded dependency was gorm.io/driver/{mysql,clickhouse,sqlite}. There was no code change in db.go.
The expectation is for db.x output to stay the same between the 2 compilations as no exported data was change. However, we observed that there were some bytes differences between the 2 .x files, which caused downstream compile actions to all rebuild.
I tried using various gcexports tools to decode the 2 files and diff them but the contents are pretty much identical. Consulting upstream Go team for more information on the 7-bytes diff.
The text was updated successfully, but these errors were encountered:
This is a tracking issue for golang/go#69547
I was upgrading our external dependencies recently and these 2 GoCompilePkg actions ran on the same package between 2 consecutive commits.
Specifically, the package is
server/util/db
with a single source filedb.go
. The upgraded dependency wasgorm.io/driver/{mysql,clickhouse,sqlite}
. There was no code change in db.go.The expectation is for
db.x
output to stay the same between the 2 compilations as no exported data was change. However, we observed that there were some bytes differences between the 2.x
files, which caused downstream compile actions to all rebuild.I tried using various gcexports tools to decode the 2 files and diff them but the contents are pretty much identical. Consulting upstream Go team for more information on the 7-bytes diff.
The text was updated successfully, but these errors were encountered: