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

Better mock server concurrency handling for put / patch processing #4931

Closed
shawkins opened this issue Feb 28, 2023 · 0 comments
Closed

Better mock server concurrency handling for put / patch processing #4931

shawkins opened this issue Feb 28, 2023 · 0 comments
Assignees
Milestone

Comments

@shawkins
Copy link
Contributor

Just like the put, delete handling, the entire processing of a put / patch should be synchronized against the resource map to prevent both the possibility of an NPE when the item is temporarily removed or a non-serialized event processing (simultaneous puts for example that both pass their optimistic locking check).

shawkins added a commit to shawkins/kubernetes-client that referenced this issue Mar 2, 2023
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Mar 6, 2023
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Mar 6, 2023
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Mar 6, 2023
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Mar 6, 2023
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Mar 6, 2023
@manusa manusa added this to the 6.5.0 milestone Mar 7, 2023
@manusa manusa closed this as completed in d75a4f6 Mar 9, 2023
manusa added a commit that referenced this issue Mar 9, 2023
fix #4931: using coarse locking to prevent odd concurrent behavior
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants