Open knz opened 1 year ago
I wonder if our 1.17
version in our go.mod
means that some libraries we're pulling in aren't getting appropriately upgraded versions (of golang.org/x/tools
for example?) that can deal with 1.18+ features.
I think we'd be comfortable upgrading go.mod to use 1.18
as ver requirement after we get #86049 merged. That would tell us more.
We have marked this issue as stale because it has been inactive for 18 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 10 days to keep the issue queue tidy. Thank you for your contribution to CockroachDB!
Describe the problem
An earlier version of PR #86457 imported
github.com/rivo/uniseg
at version 0.3, which uses go 1.18 templates (in its source fileproperties.go
).When this code is imported inside crdb, the CI build fails with:
Please describe the issue you observed, and any steps we can take to reproduce it:
Expected behavior
Upstream dependencies containing go 1.18 templates should not cause a nogo failure.
Jira issue: CRDB-19339 Epic CRDB-17171