Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with IgnoredFields in merge.Updater when using apimachinery #185

Open
nkokubo318 opened this issue Nov 5, 2024 · 2 comments
Open
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@nkokubo318
Copy link

Hey Team!

I've encountered an issue when using apimachinery version v0.31.2.

The following error occurs:

../../../../../go/pkg/mod/k8s.io/[email protected]/pkg/util/managedfields/internal/structuredmerge.go:56:4: unknown field IgnoredFields in struct literal of type merge.Updater
../../../../../go/pkg/mod/k8s.io/[email protected]/pkg/util/managedfields/internal/structuredmerge.go:73:4: unknown field IgnoredFields in struct literal of type merge.Updater

It appears that from structured-merge-diff v4.4.2 (a dependency), the IgnoredFields field was removed. After updating the modules, the above error started occurring.

For now, I’ve downgraded structured-merge-diff to v4.4.1 by running the following command:

❯ go get sigs.k8s.io/structured-merge-diff/[email protected]

Thank you to all the contributors! I appreciate any guidance on a long-term solution.

@nekomeowww
Copy link

Encountered this

unknown field IgnoredFields in struct literal of type merge.Updater

today, detail:

go build ./... 
# k8s.io/apimachinery/pkg/util/managedfields/internal
../../../../pkg/mod/k8s.io/[email protected]/pkg/util/managedfields/internal/structuredmerge.go:56:4: unknown field IgnoredFields in struct literal of type merge.Updater
../../../../pkg/mod/k8s.io/[email protected]/pkg/util/managedfields/internal/structuredmerge.go:73:4: unknown field IgnoredFields in struct literal of type merge.Updater

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants