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

FINERACT-1926: Fix No Such Element exception in Asset buyback #3859

Merged
merged 1 commit into from
Apr 19, 2024

Conversation

alberto-art3ch
Copy link
Contributor

Description

There is a NoSuchElementException when the Loan COB is executed in some specific scenario.

FINERACT-1926

Screenshot 2024-04-10 at 6 13 09 p m

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Write the commit message as per https://github.com/apache/fineract/#pull-requests

  • Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

  • Create/update unit or integration tests for verifying the changes made.

  • Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

  • Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

  • Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

try {
handleBuyback(loan, settlementDate, transfer);
} catch (ExternalAssetOwnerTransferNotFoundException e) {
log.error(e.getMessage());
Copy link
Contributor

@adamsaghy adamsaghy Apr 11, 2024

Choose a reason for hiding this comment

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

I would not use try catch for this. Please consider removing the logging and move the entry creation back to the handleBuyback method and instead of throwing an error, just execute these.

Also please dont forget you need send business events from the CANCELLED status change too!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done! code updated based on our conversation

@adamsaghy
Copy link
Contributor

@alberto-art3ch I dont see any testing!
Please consider writing unit tests to cover this new behaviour!
The test should check whether properly handled the CANCELLATION if there is no ACTIVE transfer and whether business event was sent about the CANCELLATION too!

Copy link
Contributor

@adamsaghy adamsaghy left a comment

Choose a reason for hiding this comment

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

Kindly see my review comments!

@alberto-art3ch alberto-art3ch force-pushed the fix/nee_asset_buyback_cob branch from 2046184 to ef8a8b4 Compare April 17, 2024 12:48
Copy link
Contributor

@adamsaghy adamsaghy left a comment

Choose a reason for hiding this comment

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

LGTM

@alberto-art3ch alberto-art3ch force-pushed the fix/nee_asset_buyback_cob branch from c9f1e82 to 473dbd8 Compare April 18, 2024 14:42
@alberto-art3ch alberto-art3ch force-pushed the fix/nee_asset_buyback_cob branch from 473dbd8 to 134f0c9 Compare April 18, 2024 21:22
@adamsaghy adamsaghy merged commit ce2f05e into apache:develop Apr 19, 2024
9 checks passed
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