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

Fix issue #381 #402

Merged
merged 1 commit into from
Jan 27, 2025
Merged

Fix issue #381 #402

merged 1 commit into from
Jan 27, 2025

Conversation

w-masahiro-ct
Copy link
Contributor

I have fixed Issue #381.
However, since I don't know how to reproduce Issue #381, I haven't been able to confirm the bug.
Therefore, I cannot guarantee that this pull request will completely resolve Issue #381.
That said, I have replaced the implementation with a non-destructive method, so at the very least, it should serve as a refactoring improvement.

@jcantrill
Copy link
Contributor

However, since I don't know how to reproduce Issue #381

I suspect this issue is very difficult to reproduce since it fundamentally is a race condition. Maybe it occurs when here are multiple call backs for the same pod but the cache is fundamentally a singleton ? I thought the LRU cache was additionally thread safe but maybe not.

I can accept the change and do not see it introducing a regression

@jcantrill
Copy link
Contributor

Merging as all tests are passing

@jcantrill jcantrill merged commit 8184b8a into fabric8io:master Jan 27, 2025
8 checks passed
@jcantrill
Copy link
Contributor

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

Successfully merging this pull request may close these issues.

2 participants