Skip to content

V6 - Thread safety - PaymentMethodProvider #2229

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

araratthehero
Copy link
Contributor

Description

In general Initializers should run sequentially, but it is future proof to support thread safety, in case we register factories from a different location or if in the future initializer logic change.

  • Added thread safety to the PaymentMethodProvider. In a future PR we will add the same for ActionComponentProvider.
  • Used ConcurrentHashMap Java class, since Kotlin does not have an equivalent. As an alternative Kotlin synchronized(lock) could be used, but we need to wrap every operation with it, which is more error prone.
  • Written tests for PaymentMethodProvider, including concurrency operations.

Checklist

  • Code is unit tested
  • Changes are tested manually

COSDK-550

@araratthehero araratthehero requested a review from a team as a code owner July 17, 2025 13:35
@AdyenAutomationBot AdyenAutomationBot added the Chore [PRs only] Indicates any task that does not need to be mentioned in the public release notes label Jul 17, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @araratthehero, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the robustness and reliability of the PaymentMethodProvider by introducing thread-safety measures. The core change involves migrating the internal factory storage to a ConcurrentHashMap, which inherently handles concurrent access. This enhancement is complemented by the addition of new test utilities and a comprehensive suite of unit tests, including specific concurrency tests, to ensure the stability and correctness of the changes.

Highlights

  • Enhanced Thread Safety: The PaymentMethodProvider has been updated to use ConcurrentHashMap for its internal factory storage. This change ensures thread-safe registration and retrieval of payment method factories, proactively addressing potential concurrency issues, especially if factory registration patterns evolve.
  • Testability Improvements: New internal utility methods, clear() and getFactoriesCount(), have been added to PaymentMethodProvider. These methods are annotated with @VisibleForTesting and are specifically designed to facilitate better control and verification of the provider's state in unit tests.
  • Comprehensive Unit Testing: A new dedicated test file, PaymentMethodProviderTest.kt, has been introduced. It includes extensive unit tests covering various scenarios, most notably a concurrency test to validate the thread-safe behavior of the register method, along with tests for factory registration, retrieval, overwriting, and clearing.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@araratthehero araratthehero force-pushed the chore/make_initializers_thread_safe branch from 5bf42de to a6d024d Compare July 17, 2025 13:36
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces thread safety to the PaymentMethodProvider using ConcurrentHashMap and includes comprehensive tests. I've provided suggestions to align the code with Kotlin idioms.

@araratthehero araratthehero force-pushed the chore/make_initializers_thread_safe branch from a6d024d to f3f653e Compare July 17, 2025 13:38
@araratthehero araratthehero force-pushed the chore/action_handling_change_delegate_to_component branch 4 times, most recently from 4499013 to cbea357 Compare July 18, 2025 12:32
Base automatically changed from chore/action_handling_change_delegate_to_component to main July 18, 2025 12:45
@araratthehero araratthehero force-pushed the chore/make_initializers_thread_safe branch from f3f653e to 68175c3 Compare July 18, 2025 12:59
Copy link
Contributor

✅ No public API changes

Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chore [PRs only] Indicates any task that does not need to be mentioned in the public release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants