-
Notifications
You must be signed in to change notification settings - Fork 57
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
Revert backwards incompatible changes #224
Revert backwards incompatible changes #224
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: apelisse The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
schema/elements.go
Outdated
lockOnce sync.Once | ||
// Lock which protects writes to resolvedTypes. Used as pointer so that | ||
// schema may be used as a value type | ||
lock *sync.Mutex |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need all these locks here? Can we make the lock by value since we're not supposed to copy a schema?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah there were no unsafe schema usages in the ptr semantics refactor nor in k8s/openapi usage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can remove the once. just need the lock
/hold tentative lgtm |
/unhold |
OK I've tried to fix the tags, done this:
|
Can we live with that? Everything still passes, but at least we don't have to bump the major, so any backport/cherry-pick will be much easier to sell.