[jira] [Created] (FINCN-354) Integrate and Deploy Federated model
Yemdjih Kaze Nasser created FINCN-354: - Summary: Integrate and Deploy Federated model Key: FINCN-354 URL: https://issues.apache.org/jira/browse/FINCN-354 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Yemdjih Kaze Nasser The focus here will be to productionize the Federated learning model by doing a reference implementation with Fineract 1.x and Mifos Web-App. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (FINCN-252) Machine Learning Scorecard for Credit Risk Assessment Phase 5
[ https://issues.apache.org/jira/browse/FINCN-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINCN-252: -- Summary: Machine Learning Scorecard for Credit Risk Assessment Phase 5 (was: Machine Learning Scorecard for Credit Risk Assessment Phase 4) > Machine Learning Scorecard for Credit Risk Assessment Phase 5 > - > > Key: FINCN-252 > URL: https://issues.apache.org/jira/browse/FINCN-252 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-ml >Reporter: Ed Cable >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: gsoc2021, mentor > > h2. Mentors > * Lalit Mohan S > * [~Fintecheando] > h2. Overview & Objectives > Financial Organizations using Mifos/Fineract are depending on external > agencies or their past experiences for evaluating credit scoring and > identification of potential NPAs. Though information from external agencies > is required, financial organizations can have an internal scorecard for > evaluating loans so that preventive/proactive actions can be done along with > external agencies reports. In industry, organizations are using rule based, > Statistical and Machine learning methods for credit scoring, predicting > potential NPAs, fraud detection and other activities. This project aims to > implement a scorecard based on statistical and ML methods for credit scoring > and identification of potential NPAs. > h2. Description > The approach should factor and improve last year's GSOC work > ([https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7]) > on Features/Characteristics, Criteria and evaluation (link). The design and > implementation of the screens should follow Mifos Application standards. > Should implement statistical and ML methods with explainability on decision > making. Should also be extensible for adding other functionalities such as > fraud detection, cross-sell and up-sell, etc. > h2. Helpful Skills > JAVA, Integrating Backend Service, MIFOS X, Apache Fineract, AngularJS, ORM, > ML, Statistical Methods, Django > h2. Impact > Streamlined Operations, Better RISK Management, Automated Response Mechanism > h2. Other Resources > 2019 Progress: > [https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7] > [https://gist.github.com/lalitsanagavarapu] > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (FINCN-252) Machine Learning Scorecard for Credit Risk Assessment Phase 5
[ https://issues.apache.org/jira/browse/FINCN-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-252: - Assignee: (was: Yemdjih Kaze Nasser) > Machine Learning Scorecard for Credit Risk Assessment Phase 5 > - > > Key: FINCN-252 > URL: https://issues.apache.org/jira/browse/FINCN-252 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-ml >Reporter: Ed Cable >Priority: Major > Labels: gsoc2021, mentor > > h2. Mentors > * Lalit Mohan S > * [~Fintecheando] > h2. Overview & Objectives > Financial Organizations using Mifos/Fineract are depending on external > agencies or their past experiences for evaluating credit scoring and > identification of potential NPAs. Though information from external agencies > is required, financial organizations can have an internal scorecard for > evaluating loans so that preventive/proactive actions can be done along with > external agencies reports. In industry, organizations are using rule based, > Statistical and Machine learning methods for credit scoring, predicting > potential NPAs, fraud detection and other activities. This project aims to > implement a scorecard based on statistical and ML methods for credit scoring > and identification of potential NPAs. > h2. Description > The approach should factor and improve last year's GSOC work > ([https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7]) > on Features/Characteristics, Criteria and evaluation (link). The design and > implementation of the screens should follow Mifos Application standards. > Should implement statistical and ML methods with explainability on decision > making. Should also be extensible for adding other functionalities such as > fraud detection, cross-sell and up-sell, etc. > h2. Helpful Skills > JAVA, Integrating Backend Service, MIFOS X, Apache Fineract, AngularJS, ORM, > ML, Statistical Methods, Django > h2. Impact > Streamlined Operations, Better RISK Management, Automated Response Mechanism > h2. Other Resources > 2019 Progress: > [https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7] > [https://gist.github.com/lalitsanagavarapu] > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (FINCN-351) Make the scorecard integration into a plugin
Yemdjih Kaze Nasser created FINCN-351: - Summary: Make the scorecard integration into a plugin Key: FINCN-351 URL: https://issues.apache.org/jira/browse/FINCN-351 Project: Fineract Cloud Native Issue Type: Bug Reporter: Yemdjih Kaze Nasser Instead of having the scorecard jar into the fineract project where it could add some extra complications and at distribution level and the system reliability, We figured it's best the scorecard integration takes the form of a plugin like it is done with pentaho. see [openMF/fineract-pentaho: Pentaho Reporting Plugin for Apache Fineract (github.com)|https://github.com/openMF/fineract-pentaho#license] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINCN-351) Make the scorecard integration into a plugin
[ https://issues.apache.org/jira/browse/FINCN-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINCN-351: -- Issue Type: Improvement (was: Bug) > Make the scorecard integration into a plugin > > > Key: FINCN-351 > URL: https://issues.apache.org/jira/browse/FINCN-351 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Yemdjih Kaze Nasser >Priority: Major > > Instead of having the scorecard jar into the fineract project where it could > add some extra complications and at distribution level and the system > reliability, We figured it's best the scorecard integration takes the form of > a plugin like it is done with pentaho. see [openMF/fineract-pentaho: Pentaho > Reporting Plugin for Apache Fineract > (github.com)|https://github.com/openMF/fineract-pentaho#license] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-351) Make the scorecard integration into a plugin
[ https://issues.apache.org/jira/browse/FINCN-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-351: - Assignee: Yemdjih Kaze Nasser > Make the scorecard integration into a plugin > > > Key: FINCN-351 > URL: https://issues.apache.org/jira/browse/FINCN-351 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Instead of having the scorecard jar into the fineract project where it could > add some extra complications and at distribution level and the system > reliability, We figured it's best the scorecard integration takes the form of > a plugin like it is done with pentaho. see [openMF/fineract-pentaho: Pentaho > Reporting Plugin for Apache Fineract > (github.com)|https://github.com/openMF/fineract-pentaho#license] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINCN-252) Machine Learning Scorecard for Credit Risk Assessment Phase 4
[ https://issues.apache.org/jira/browse/FINCN-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394554#comment-17394554 ] Yemdjih Kaze Nasser commented on FINCN-252: --- Thanks for creating the repository, will push the changes there ASAP. > Machine Learning Scorecard for Credit Risk Assessment Phase 4 > - > > Key: FINCN-252 > URL: https://issues.apache.org/jira/browse/FINCN-252 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Ed Cable >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: gsoc2021, mentor > > h2. Mentors > * Lalit Mohan S > * [~Fintecheando] > h2. Overview & Objectives > Financial Organizations using Mifos/Fineract are depending on external > agencies or their past experiences for evaluating credit scoring and > identification of potential NPAs. Though information from external agencies > is required, financial organizations can have an internal scorecard for > evaluating loans so that preventive/proactive actions can be done along with > external agencies reports. In industry, organizations are using rule based, > Statistical and Machine learning methods for credit scoring, predicting > potential NPAs, fraud detection and other activities. This project aims to > implement a scorecard based on statistical and ML methods for credit scoring > and identification of potential NPAs. > h2. Description > The approach should factor and improve last year's GSOC work > ([https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7]) > on Features/Characteristics, Criteria and evaluation (link). The design and > implementation of the screens should follow Mifos Application standards. > Should implement statistical and ML methods with explainability on decision > making. Should also be extensible for adding other functionalities such as > fraud detection, cross-sell and up-sell, etc. > h2. Helpful Skills > JAVA, Integrating Backend Service, MIFOS X, Apache Fineract, AngularJS, ORM, > ML, Statistical Methods, Django > h2. Impact > Streamlined Operations, Better RISK Management, Automated Response Mechanism > h2. Other Resources > 2019 Progress: > [https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7] > [https://gist.github.com/lalitsanagavarapu] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINCN-331) Import statistical scoring in the API
[ https://issues.apache.org/jira/browse/FINCN-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17393796#comment-17393796 ] Yemdjih Kaze Nasser commented on FINCN-331: --- There's no PR yet but the work is reflected across 3 different repos, one of which is not yet under the Mifos nor the Apache organisation. > Import statistical scoring in the API > - > > Key: FINCN-331 > URL: https://issues.apache.org/jira/browse/FINCN-331 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Import and implement and test statistical scoring from last iteration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINCN-331) Import statistical scoring in the API
[ https://issues.apache.org/jira/browse/FINCN-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINCN-331. --- Resolution: Done > Import statistical scoring in the API > - > > Key: FINCN-331 > URL: https://issues.apache.org/jira/browse/FINCN-331 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Import and implement and test statistical scoring from last iteration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-331) Import statistical scoring in the API
[ https://issues.apache.org/jira/browse/FINCN-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-331: - Assignee: Yemdjih Kaze Nasser > Import statistical scoring in the API > - > > Key: FINCN-331 > URL: https://issues.apache.org/jira/browse/FINCN-331 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Import and implement and test statistical scoring from last iteration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-329) Integrate scorecard configurations
[ https://issues.apache.org/jira/browse/FINCN-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-329: - Assignee: Yemdjih Kaze Nasser > Integrate scorecard configurations > -- > > Key: FINCN-329 > URL: https://issues.apache.org/jira/browse/FINCN-329 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Migrate scorecard configurations from last years work into the new module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINCN-329) Integrate scorecard configurations
[ https://issues.apache.org/jira/browse/FINCN-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINCN-329. --- Resolution: Implemented > Integrate scorecard configurations > -- > > Key: FINCN-329 > URL: https://issues.apache.org/jira/browse/FINCN-329 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Migrate scorecard configurations from last years work into the new module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-332) Import Machine Learing scoring
[ https://issues.apache.org/jira/browse/FINCN-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-332: - Assignee: Yemdjih Kaze Nasser > Import Machine Learing scoring > --- > > Key: FINCN-332 > URL: https://issues.apache.org/jira/browse/FINCN-332 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Import and implement and test machine learning scoring in the API module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINCN-330) Import rule based in the API.
[ https://issues.apache.org/jira/browse/FINCN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINCN-330. --- Resolution: Implemented > Import rule based in the API. > - > > Key: FINCN-330 > URL: https://issues.apache.org/jira/browse/FINCN-330 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Import and implement and test rule based scoring in the API module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINCN-332) Import Machine Learing scoring
[ https://issues.apache.org/jira/browse/FINCN-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINCN-332. --- Resolution: Implemented > Import Machine Learing scoring > --- > > Key: FINCN-332 > URL: https://issues.apache.org/jira/browse/FINCN-332 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Priority: Major > > Import and implement and test machine learning scoring in the API module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-330) Import rule based in the API.
[ https://issues.apache.org/jira/browse/FINCN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-330: - Assignee: Yemdjih Kaze Nasser > Import rule based in the API. > - > > Key: FINCN-330 > URL: https://issues.apache.org/jira/browse/FINCN-330 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Import and implement and test rule based scoring in the API module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-982) Completely ditch use of Drizzle JDBC Driver after all
[ https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-982: Assignee: (was: Yemdjih Kaze Nasser) > Completely ditch use of Drizzle JDBC Driver after all > - > > Key: FINERACT-982 > URL: https://issues.apache.org/jira/browse/FINERACT-982 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Priority: Blocker > Labels: scalability > Fix For: 1.6.0 > > > Fineract's use of the un-maintained Drizzle JDBC driver continues to cause > confusion and pains like FINERACT-980, and note e.g. the proposed removal of > the alternative MySQL JDBC driver in > [https://github.com/apache/fineract/pull/887.] > Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and > LEGAL-462. > LEGAL-462 has clarified that the Fineract ZIP distribution must include > Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and > currently (given the confusion in FINERACT-980 apparently do?!) use it for > tests. > What if to reduce variability we just removed that old Drizzle JDBC driver > after all? We could run our tests using (preferably) the very well maintained > MariaDB JDBC driver client (the actual DB server is a totally separate > discussion, see FINERACT-896). We would (have to) distribute the ZIP for > download without a JDBC driver, and just some documentation inviting users to > DL and add one. > But the exact situation about distributing in a Docker container image isn't > clear, to me... > FYI [~awasum], [~ptuomola], [~xurror] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1140) Adopt GenerationType.TABLE as ID generation strategy
[ https://issues.apache.org/jira/browse/FINERACT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-1140. --- Resolution: Won't Do > Adopt GenerationType.TABLE as ID generation strategy > > > Key: FINERACT-1140 > URL: https://issues.apache.org/jira/browse/FINERACT-1140 > Project: Apache Fineract > Issue Type: Test >Affects Versions: 1.5.0 >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Working with eclipselink, I noticed there were situations where when trying > to persist objects with sub entities, the IDs of the sub entities where not > generated fast enough making the ID column to always be set to null causing a > lot SQLIntegrityViolations. > As a solution of last resort I experimented with table generation strategy > which is able to set ID upon object creation instead of at persist time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1322) Add Support for a Bi Monthly Loan Product
[ https://issues.apache.org/jira/browse/FINERACT-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1322: - Assignee: (was: Yemdjih Kaze Nasser) > Add Support for a Bi Monthly Loan Product > - > > Key: FINERACT-1322 > URL: https://issues.apache.org/jira/browse/FINERACT-1322 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Reporter: Yemdjih Kaze Nasser >Priority: Major > Fix For: 1.6.0 > > > Add the ability to create a loan that is collected twice a month. Date > selection would be one of two options > Two dates selected for each month: default dates are already part of this > ensemble i.e 15th and 30th, 10th and 25th > These date combinations may change midway for e,g 10/25 may become 15/30, > Which means we can edit the loan product’ First and second date thus > affecting the schedule change from that day. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINCN-334) Implement and integrate scoring with H2o.ai
Yemdjih Kaze Nasser created FINCN-334: - Summary: Implement and integrate scoring with H2o.ai Key: FINCN-334 URL: https://issues.apache.org/jira/browse/FINCN-334 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Yemdjih Kaze Nasser -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINCN-333) Create ML pipeline to auto-update ML scoring
Yemdjih Kaze Nasser created FINCN-333: - Summary: Create ML pipeline to auto-update ML scoring Key: FINCN-333 URL: https://issues.apache.org/jira/browse/FINCN-333 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Yemdjih Kaze Nasser Leverage airflow and airflow dags to build an ML pipeline to keep updating the ML models with time thus keeping it relevant. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINCN-332) Import Machine Learing scoring
Yemdjih Kaze Nasser created FINCN-332: - Summary: Import Machine Learing scoring Key: FINCN-332 URL: https://issues.apache.org/jira/browse/FINCN-332 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Yemdjih Kaze Nasser Import and implement and test machine learning scoring in the API module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINCN-331) Import statistical scoring in the API
Yemdjih Kaze Nasser created FINCN-331: - Summary: Import statistical scoring in the API Key: FINCN-331 URL: https://issues.apache.org/jira/browse/FINCN-331 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Yemdjih Kaze Nasser Import and implement and test statistical scoring from last iteration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINCN-330) Import rule based in the API.
Yemdjih Kaze Nasser created FINCN-330: - Summary: Import rule based in the API. Key: FINCN-330 URL: https://issues.apache.org/jira/browse/FINCN-330 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Yemdjih Kaze Nasser Import and implement and test rule based scoring in the API module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINCN-329) Integrate scorecard configurations
Yemdjih Kaze Nasser created FINCN-329: - Summary: Integrate scorecard configurations Key: FINCN-329 URL: https://issues.apache.org/jira/browse/FINCN-329 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Yemdjih Kaze Nasser Migrate scorecard configurations from last years work into the new module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-252) Machine Learning Scorecard for Credit Risk Assessment Phase 4
[ https://issues.apache.org/jira/browse/FINCN-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-252: - Assignee: Yemdjih Kaze Nasser > Machine Learning Scorecard for Credit Risk Assessment Phase 4 > - > > Key: FINCN-252 > URL: https://issues.apache.org/jira/browse/FINCN-252 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Ed Cable >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: gsoc2021, mentor > > h2. Mentors > * Lalit Mohan S > * [~Fintecheando] > h2. Overview & Objectives > Financial Organizations using Mifos/Fineract are depending on external > agencies or their past experiences for evaluating credit scoring and > identification of potential NPAs. Though information from external agencies > is required, financial organizations can have an internal scorecard for > evaluating loans so that preventive/proactive actions can be done along with > external agencies reports. In industry, organizations are using rule based, > Statistical and Machine learning methods for credit scoring, predicting > potential NPAs, fraud detection and other activities. This project aims to > implement a scorecard based on statistical and ML methods for credit scoring > and identification of potential NPAs. > h2. Description > The approach should factor and improve last year's GSOC work > ([https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7]) > on Features/Characteristics, Criteria and evaluation (link). The design and > implementation of the screens should follow Mifos Application standards. > Should implement statistical and ML methods with explainability on decision > making. Should also be extensible for adding other functionalities such as > fraud detection, cross-sell and up-sell, etc. > h2. Helpful Skills > JAVA, Integrating Backend Service, MIFOS X, Apache Fineract, AngularJS, ORM, > ML, Statistical Methods, Django > h2. Impact > Streamlined Operations, Better RISK Management, Automated Response Mechanism > h2. Other Resources > 2019 Progress: > [https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7] > [https://gist.github.com/lalitsanagavarapu] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1267) NullPointerException at ChronoLocalDate.isEqual()
[
https://issues.apache.org/jira/browse/FINERACT-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319670#comment-17319670
]
Yemdjih Kaze Nasser commented on FINERACT-1267:
---
[~vorburger] Now that we've moved to Joda Time, is this still happening?
> NullPointerException at ChronoLocalDate.isEqual()
> -
>
> Key: FINERACT-1267
> URL: https://issues.apache.org/jira/browse/FINERACT-1267
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Michael Vorburger
>Priority: Blocker
>
> See FINERACT-932 for general background; I've found this in logs of
> [https://www.fineract.dev|https://www.fineract.dev]:
>
> {code:java}java.lang.NullPointerException: null
> at java.time.chrono.ChronoLocalDate.isEqual (ChronoLocalDate.java:765)
> at java.time.LocalDate.isEqual (LocalDate.java:2115)
> at
> org.apache.fineract.portfolio.savings.service.SavingsAccountWritePlatformServiceJpaRepositoryImpl.validateTransactionsForTransfer
> (SavingsAccountWritePlatformServiceJpaRepositoryImpl.java:1696)
> at
> org.apache.fineract.portfolio.savings.service.SavingsAccountWritePlatformServiceJpaRepositoryImpl.initiateSavingsTransfer
> (SavingsAccountWritePlatformServiceJpaRepositoryImpl.java:896)
> at
> org.apache.fineract.portfolio.savings.service.SavingsAccountWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$fa18015c.invoke
> ()
> at org.springframework.cglib.proxy.MethodProxy.invoke
> (MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept
> (CglibAopProxy.java:687)
> at
> org.apache.fineract.portfolio.savings.service.SavingsAccountWritePlatformServiceJpaRepositoryImpl$$EnhancerBySpringCGLIB$$c5a5819d.initiateSavingsTransfer
> ()
> at
> org.apache.fineract.portfolio.transfer.service.TransferWritePlatformServiceJpaRepositoryImpl.handleClientTransferLifecycleEvent
> (TransferWritePlatformServiceJpaRepositoryImpl.java:434)
> at
> org.apache.fineract.portfolio.transfer.service.TransferWritePlatformServiceJpaRepositoryImpl.proposeClientTransfer
> (TransferWritePlatformServiceJpaRepositoryImpl.java:317)
> at
> org.apache.fineract.portfolio.transfer.service.TransferWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$f189347f.invoke
> ()
> at org.springframework.cglib.proxy.MethodProxy.invoke
> (MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint
> (CglibAopProxy.java:771)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
> (ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed
> (CglibAopProxy.java:749)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction
> (TransactionAspectSupport.java:367)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke
> (TransactionInterceptor.java:118)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
> (ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed
> (CglibAopProxy.java:749)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept
> (CglibAopProxy.java:691)
> at
> org.apache.fineract.portfolio.transfer.service.TransferWritePlatformServiceJpaRepositoryImpl$$EnhancerBySpringCGLIB$$514a8e6.proposeClientTransfer
> ()
> at
> org.apache.fineract.portfolio.transfer.handler.ProposeClientTransferCommandHandler.processCommand
> (ProposeClientTransferCommandHandler.java:45)
> at
> org.apache.fineract.portfolio.transfer.handler.ProposeClientTransferCommandHandler$$FastClassBySpringCGLIB$$bd6f02f0.invoke
> ()
> at org.springframework.cglib.proxy.MethodProxy.invoke
> (MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint
> (CglibAopProxy.java:771)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
> (ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed
> (CglibAopProxy.java:749)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction
> (TransactionAspectSupport.java:367)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke
> (TransactionInterceptor.java:118)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
>
[jira] [Updated] (FINCN-252) Machine Learning Scorecard for Credit Risk Assessment Phase 4
[ https://issues.apache.org/jira/browse/FINCN-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINCN-252: -- Description: h2. Mentors * Lalit Mohan S * [~Fintecheando] h2. Overview & Objectives Financial Organizations using Mifos/Fineract are depending on external agencies or their past experiences for evaluating credit scoring and identification of potential NPAs. Though information from external agencies is required, financial organizations can have an internal scorecard for evaluating loans so that preventive/proactive actions can be done along with external agencies reports. In industry, organizations are using rule based, Statistical and Machine learning methods for credit scoring, predicting potential NPAs, fraud detection and other activities. This project aims to implement a scorecard based on statistical and ML methods for credit scoring and identification of potential NPAs. h2. Description The approach should factor and improve last year's GSOC work ([https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7]) on Features/Characteristics, Criteria and evaluation (link). The design and implementation of the screens should follow Mifos Application standards. Should implement statistical and ML methods with explainability on decision making. Should also be extensible for adding other functionalities such as fraud detection, cross-sell and up-sell, etc. h2. Helpful Skills JAVA, Integrating Backend Service, MIFOS X, Apache Fineract, AngularJS, ORM, ML, Statistical Methods, Django h2. Impact Streamlined Operations, Better RISK Management, Automated Response Mechanism h2. Other Resources 2019 Progress: [https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7] [https://gist.github.com/lalitsanagavarapu] was: h2. Mentors * Lalit Mohan S * [~Fintecheando] h2. Overview & Objectives Financial Organizations using Mifos/Fineract are depending on external agencies or their past experiences for evaluating credit scoring and identification of potential NPAs. Though information from external agencies is required, financial organizations can have an internal scorecard for evaluating loans so that preventive/proactive actions can be done along with external agencies reports. In industry, organizations are using rule based, Statistical and Machine learning methods for credit scoring, predicting potential NPAs, fraud detection and other activities. This project aims to implement a scorecard based on statistical and ML methods for credit scoring and identification of potential NPAs. h2. Description The approach should factor and improve last year's GSOC work (https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7) on Features/Characteristics, Criteria and evaluation (link). The design and implementation of the screens should follow Mifos Application standards. Should implement statistical and ML methods with explainability on decision making. Should also be extensible for adding other functionalities such as fraud detection, cross-sell and up-sell, etc. h2. Helpful Skills JAVA, Integrating Backend Service, MIFOS X, Apache Fineract, AngularJS, ORM, ML, Statistical Methods, Django h2. Impact Streamlined Operations, Better RISK Management, Automated Response Mechanism h2. Other Resources 2019 Progress: https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7 https://gist.github.com/lalitsanagavarapu > Machine Learning Scorecard for Credit Risk Assessment Phase 4 > - > > Key: FINCN-252 > URL: https://issues.apache.org/jira/browse/FINCN-252 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Ed Cable >Priority: Major > Labels: gsoc2021, mentor > > h2. Mentors > * Lalit Mohan S > * [~Fintecheando] > h2. Overview & Objectives > Financial Organizations using Mifos/Fineract are depending on external > agencies or their past experiences for evaluating credit scoring and > identification of potential NPAs. Though information from external agencies > is required, financial organizations can have an internal scorecard for > evaluating loans so that preventive/proactive actions can be done along with > external agencies reports. In industry, organizations are using rule based, > Statistical and Machine learning methods for credit scoring, predicting > potential NPAs, fraud detection and other activities. This project aims to > implement a scorecard based on statistical and ML methods for credit scoring > and identification of potential NPAs. > h2. Description > The approach should factor and improve last year's GSOC work >
[jira] [Commented] (FINERACT-244) New Repayment Schedule Not Populating
[ https://issues.apache.org/jira/browse/FINERACT-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17301378#comment-17301378 ] Yemdjih Kaze Nasser commented on FINERACT-244: -- Tried this in the demo server and the view populates properly. If you still facing this issue you try using the latest develop code or the very soon coming 1.5.0 release. > New Repayment Schedule Not Populating > - > > Key: FINERACT-244 > URL: https://issues.apache.org/jira/browse/FINERACT-244 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: Volunteer, confirm, gsoc > Fix For: 1.5.0 > > > Mifos - View Loan Account - More Drop Down - Reschedule > After complete Reschedule Loan Screen - Press Submit > View Loan reschedule request - then select View new Repayment Schedule > New Repayment Schedule Screen does not populate any information for > verification prior to accepting the change. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-244) New Repayment Schedule Not Populating
[ https://issues.apache.org/jira/browse/FINERACT-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-244. -- Assignee: Yemdjih Kaze Nasser Resolution: Cannot Reproduce > New Repayment Schedule Not Populating > - > > Key: FINERACT-244 > URL: https://issues.apache.org/jira/browse/FINERACT-244 > Project: Apache Fineract > Issue Type: Bug >Reporter: Dayna Harp >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: Volunteer, confirm, gsoc > Fix For: 1.5.0 > > > Mifos - View Loan Account - More Drop Down - Reschedule > After complete Reschedule Loan Screen - Press Submit > View Loan reschedule request - then select View new Repayment Schedule > New Repayment Schedule Screen does not populate any information for > verification prior to accepting the change. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-998) Validate Spring Data JPA *Repository methods
[
https://issues.apache.org/jira/browse/FINERACT-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser updated FINERACT-998:
-
Description:
In [https://github.com/apache/fineract/pull/925] for FINERACT-997, [~saransh]
noticed that, apparently, the {{ProductToGLAccountMappingRepository}} had a
subtle method naming bug which made the query always return empty.
This made me curious if there wasn't something to make Spring Data JPA detect
this kind of problem by itself either (better) at build time, or (also OK)
while it starts up and component scans at runtime, and log a clear (ideally
fatal..) error about it.
Maybe this isn't possible, but it strikes me as a basic check Spring should do.
was:
In [https://github.com/apache/fineract/pull/925] for FINERACT-997, [~saransh]
noticed that, apparently, the {{ProductToGLAccountMappingRepository}} had a
subtle method naming bug which made the query always return empty.
This made me curious if there wasn't something to make Spring Data JPA detect
this kind of problem by itself either (better) at build time, or (also OK)
while it starts up and component scans at runtime, and log a clear (ideally
fatal..) error about it.
Maybe this isn't possible, but it strikes me as a basic check Spring should do.
> Validate Spring Data JPA *Repository methods
>
>
> Key: FINERACT-998
> URL: https://issues.apache.org/jira/browse/FINERACT-998
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Michael Vorburger
>Priority: Critical
>
> In [https://github.com/apache/fineract/pull/925] for FINERACT-997, [~saransh]
> noticed that, apparently, the {{ProductToGLAccountMappingRepository}} had a
> subtle method naming bug which made the query always return empty.
> This made me curious if there wasn't something to make Spring Data JPA detect
> this kind of problem by itself either (better) at build time, or (also OK)
> while it starts up and component scans at runtime, and log a clear (ideally
> fatal..) error about it.
> Maybe this isn't possible, but it strikes me as a basic check Spring should
> do.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-982) Completely ditch use of Drizzle JDBC Driver after all
[ https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292494#comment-17292494 ] Yemdjih Kaze Nasser commented on FINERACT-982: -- It's in progress now, PR has gone stale though. I'd like to give it another try. Expect a PR for this in a few hours. > Completely ditch use of Drizzle JDBC Driver after all > - > > Key: FINERACT-982 > URL: https://issues.apache.org/jira/browse/FINERACT-982 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Assignee: Yemdjih Kaze Nasser >Priority: Blocker > Labels: scalability > Fix For: 1.5.0 > > > Fineract's use of the un-maintained Drizzle JDBC driver continues to cause > confusion and pains like FINERACT-980, and note e.g. the proposed removal of > the alternative MySQL JDBC driver in > [https://github.com/apache/fineract/pull/887.] > Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and > LEGAL-462. > LEGAL-462 has clarified that the Fineract ZIP distribution must include > Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and > currently (given the confusion in FINERACT-980 apparently do?!) use it for > tests. > What if to reduce variability we just removed that old Drizzle JDBC driver > after all? We could run our tests using (preferably) the very well maintained > MariaDB JDBC driver client (the actual DB server is a totally separate > discussion, see FINERACT-896). We would (have to) distribute the ZIP for > download without a JDBC driver, and just some documentation inviting users to > DL and add one. > But the exact situation about distributing in a Docker container image isn't > clear, to me... > FYI [~awasum], [~ptuomola], [~xurror] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-982) Completely ditch use of Drizzle JDBC Driver after all
[ https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292487#comment-17292487 ] Yemdjih Kaze Nasser commented on FINERACT-982: -- If I'm not mistaken, the docker build from before allowed an option to use mysql-connector for a containerized run. I think the issue with using mysql/mariadb connector in dev environment like for running tests still persists. Unless I've failed to really understand how FINERACT-1177 works, I think this still persists to some extent. > Completely ditch use of Drizzle JDBC Driver after all > - > > Key: FINERACT-982 > URL: https://issues.apache.org/jira/browse/FINERACT-982 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Assignee: Yemdjih Kaze Nasser >Priority: Blocker > Labels: scalability > Fix For: 1.5.0 > > > Fineract's use of the un-maintained Drizzle JDBC driver continues to cause > confusion and pains like FINERACT-980, and note e.g. the proposed removal of > the alternative MySQL JDBC driver in > [https://github.com/apache/fineract/pull/887.] > Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and > LEGAL-462. > LEGAL-462 has clarified that the Fineract ZIP distribution must include > Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and > currently (given the confusion in FINERACT-980 apparently do?!) use it for > tests. > What if to reduce variability we just removed that old Drizzle JDBC driver > after all? We could run our tests using (preferably) the very well maintained > MariaDB JDBC driver client (the actual DB server is a totally separate > discussion, see FINERACT-896). We would (have to) distribute the ZIP for > download without a JDBC driver, and just some documentation inviting users to > DL and add one. > But the exact situation about distributing in a Docker container image isn't > clear, to me... > FYI [~awasum], [~ptuomola], [~xurror] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1322) Add Support for a Bi Monthly Loan Product
[ https://issues.apache.org/jira/browse/FINERACT-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1322: - Assignee: Yemdjih Kaze Nasser > Add Support for a Bi Monthly Loan Product > - > > Key: FINERACT-1322 > URL: https://issues.apache.org/jira/browse/FINERACT-1322 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Add the ability to create a loan that is collected twice a month. Date > selection would be one of two options > Two dates selected for each month: default dates are already part of this > ensemble i.e 15th and 30th, 10th and 25th > These date combinations may change midway for e,g 10/25 may become 15/30, > Which means we can edit the loan product’ First and second date thus > affecting the schedule change from that day. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1322) Add Support for a Bi Monthly Loan Product
Yemdjih Kaze Nasser created FINERACT-1322: - Summary: Add Support for a Bi Monthly Loan Product Key: FINERACT-1322 URL: https://issues.apache.org/jira/browse/FINERACT-1322 Project: Apache Fineract Issue Type: New Feature Components: Loan Reporter: Yemdjih Kaze Nasser Add the ability to create a loan that is collected twice a month. Date selection would be one of two options Two dates selected for each month: default dates are already part of this ensemble i.e 15th and 30th, 10th and 25th These date combinations may change midway for e,g 10/25 may become 15/30, Which means we can edit the loan product’ First and second date thus affecting the schedule change from that day. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink
[ https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINERACT-849: - Fix Version/s: (was: 1.5.0) > Migrate Fineract ORM from OpenJPA to EclipseLink > > > Key: FINERACT-849 > URL: https://issues.apache.org/jira/browse/FINERACT-849 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ed Cable >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: gsoc2020, hard, mentor, technical > > In line with the rationale for choosing EclipseLink as the ORM replacement > for Hibernate in FineractCN, we have broad consensus across the community to > swap out OpenJPA with EclipseLink. > OpenJPA seems to have reached its end of life with community activity > withering and the trade-offs between Hibernate and EclipseLink are much > lower. We also have community members who are migrating Fineract 1.x to > PostGreSQL and would benefit from the increased performance with EclipseLink. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (FINERACT-1292) Needs to add ReadinessProbe for MySql pod
[ https://issues.apache.org/jira/browse/FINERACT-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reopened FINERACT-1292: --- > Needs to add ReadinessProbe for MySql pod > - > > Key: FINERACT-1292 > URL: https://issues.apache.org/jira/browse/FINERACT-1292 > Project: Apache Fineract > Issue Type: Task >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > In mysql deployment it's better to add ReadinessProbe which tells when the > container will be available for accepting traffic. This can be achieved by > using a command like `mysqladmin ping -u -p` to check whether > a mysql user has been properly created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1292) Needs to add ReadinessProbe for MySql pod
[ https://issues.apache.org/jira/browse/FINERACT-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-1292. --- Resolution: Fixed > Needs to add ReadinessProbe for MySql pod > - > > Key: FINERACT-1292 > URL: https://issues.apache.org/jira/browse/FINERACT-1292 > Project: Apache Fineract > Issue Type: Task >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > In mysql deployment it's better to add ReadinessProbe which tells when the > container will be available for accepting traffic. This can be achieved by > using a command like `mysqladmin ping -u -p` to check whether > a mysql user has been properly created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1258) NPE at LoanAccountDomainServiceJpa.recalculateAccruals()
[
https://issues.apache.org/jira/browse/FINERACT-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239108#comment-17239108
]
Yemdjih Kaze Nasser commented on FINERACT-1258:
---
[~vorburger] I believe this issue has met its fix with the new tenant time zone
implementation brought about after migrating Joda time to java time.
I think it's safe to close this unless it's still happening.
> NPE at LoanAccountDomainServiceJpa.recalculateAccruals()
>
>
> Key: FINERACT-1258
> URL: https://issues.apache.org/jira/browse/FINERACT-1258
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Michael Vorburger
>Assignee: Yemdjih Kaze Nasser
>Priority: Blocker
> Labels: technical
>
> See FINERACT-932 for general background; I've found this in logs of
> https://www.fineract.dev:
> {code}
> java.lang.NullPointerException
> at
> org.apache.fineract.portfolio.loanaccount.domain.LoanAccountDomainServiceJpa.recalculateAccruals
> (LoanAccountDomainServiceJpa.java:511)
> at
> org.apache.fineract.portfolio.loanaccount.domain.LoanAccountDomainServiceJpa.recalculateAccruals
> (LoanAccountDomainServiceJpa.java:476)
> at
> org.apache.fineract.portfolio.loanaccount.domain.LoanAccountDomainServiceJpa$$FastClassBySpringCGLIB$$526a2072.invoke
> ()
> at org.springframework.cglib.proxy.MethodProxy.invoke
> (MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept
> (CglibAopProxy.java:687)
> at
> org.apache.fineract.portfolio.loanaccount.domain.LoanAccountDomainServiceJpa$$EnhancerBySpringCGLIB$$15a35201.recalculateAccruals
> ()
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanWritePlatformServiceJpaRepositoryImpl.recalculateInterest
> (LoanWritePlatformServiceJpaRepositoryImpl.java:2867)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$cb835224.invoke
> ()
> at org.springframework.cglib.proxy.MethodProxy.invoke
> (MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint
> (CglibAopProxy.java:771)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
> (ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed
> (CglibAopProxy.java:749)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction
> (TransactionAspectSupport.java:367)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke
> (TransactionInterceptor.java:118)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
> (ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed
> (CglibAopProxy.java:749)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept
> (CglibAopProxy.java:691)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanWritePlatformServiceJpaRepositoryImpl$$EnhancerBySpringCGLIB$$dfda8657.recalculateInterest
> ()
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanSchedularServiceImpl.recalculateInterest
> (LoanSchedularServiceImpl.java:138)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native
> Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.springframework.util.MethodInvoker.invoke
> (MethodInvoker.java:283)
> at
> org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal
> (MethodInvokingJobDetailFactoryBean.java:267)
> at org.springframework.scheduling.quartz.QuartzJobBean.execute
> (QuartzJobBean.java:75)
> at org.quartz.core.JobRunShell.run (JobRunShell.java:202)
> at org.quartz.simpl.SimpleThreadPool$WorkerThread.run
> (SimpleThreadPool.java:573){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FINERACT-1258) NPE at LoanAccountDomainServiceJpa.recalculateAccruals()
[
https://issues.apache.org/jira/browse/FINERACT-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser reassigned FINERACT-1258:
-
Assignee: Yemdjih Kaze Nasser
> NPE at LoanAccountDomainServiceJpa.recalculateAccruals()
>
>
> Key: FINERACT-1258
> URL: https://issues.apache.org/jira/browse/FINERACT-1258
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Michael Vorburger
>Assignee: Yemdjih Kaze Nasser
>Priority: Blocker
> Labels: technical
>
> See FINERACT-932 for general background; I've found this in logs of
> https://www.fineract.dev:
> {code}
> java.lang.NullPointerException
> at
> org.apache.fineract.portfolio.loanaccount.domain.LoanAccountDomainServiceJpa.recalculateAccruals
> (LoanAccountDomainServiceJpa.java:511)
> at
> org.apache.fineract.portfolio.loanaccount.domain.LoanAccountDomainServiceJpa.recalculateAccruals
> (LoanAccountDomainServiceJpa.java:476)
> at
> org.apache.fineract.portfolio.loanaccount.domain.LoanAccountDomainServiceJpa$$FastClassBySpringCGLIB$$526a2072.invoke
> ()
> at org.springframework.cglib.proxy.MethodProxy.invoke
> (MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept
> (CglibAopProxy.java:687)
> at
> org.apache.fineract.portfolio.loanaccount.domain.LoanAccountDomainServiceJpa$$EnhancerBySpringCGLIB$$15a35201.recalculateAccruals
> ()
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanWritePlatformServiceJpaRepositoryImpl.recalculateInterest
> (LoanWritePlatformServiceJpaRepositoryImpl.java:2867)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$cb835224.invoke
> ()
> at org.springframework.cglib.proxy.MethodProxy.invoke
> (MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint
> (CglibAopProxy.java:771)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
> (ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed
> (CglibAopProxy.java:749)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction
> (TransactionAspectSupport.java:367)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke
> (TransactionInterceptor.java:118)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
> (ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed
> (CglibAopProxy.java:749)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept
> (CglibAopProxy.java:691)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanWritePlatformServiceJpaRepositoryImpl$$EnhancerBySpringCGLIB$$dfda8657.recalculateInterest
> ()
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanSchedularServiceImpl.recalculateInterest
> (LoanSchedularServiceImpl.java:138)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native
> Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.springframework.util.MethodInvoker.invoke
> (MethodInvoker.java:283)
> at
> org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal
> (MethodInvokingJobDetailFactoryBean.java:267)
> at org.springframework.scheduling.quartz.QuartzJobBean.execute
> (QuartzJobBean.java:75)
> at org.quartz.core.JobRunShell.run (JobRunShell.java:202)
> at org.quartz.simpl.SimpleThreadPool$WorkerThread.run
> (SimpleThreadPool.java:573){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-756) Scheduler job fails If we enter date manually without using date-picker
[ https://issues.apache.org/jira/browse/FINERACT-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239089#comment-17239089 ] Yemdjih Kaze Nasser commented on FINERACT-756: -- This is probably a problem with date format which subsequently sends invalid date input to the backend hence this will keep occurring. Using the date picker is just safer. > Scheduler job fails If we enter date manually without using date-picker > --- > > Key: FINERACT-756 > URL: https://issues.apache.org/jira/browse/FINERACT-756 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.3.0 >Reporter: Santosh Math >Priority: Major > Labels: p1 > Fix For: 1.5.0 > > > 1) Go to any savings account and click on 'More' > 2) Select 'Add Charge' , give the inputs (select the weekly fee) and enter > the date 'Due for Collection on' manually , ie.. by typing it. Don't use > date-picker. > > If you run the scheduler job 'Pay Due for Savings' , it's failing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1069) RecurringDepositTest / FixedDepositTests failing on 1st of month
[ https://issues.apache.org/jira/browse/FINERACT-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1069: - Assignee: (was: Yemdjih Kaze Nasser) > RecurringDepositTest / FixedDepositTests failing on 1st of month > > > Key: FINERACT-1069 > URL: https://issues.apache.org/jira/browse/FINERACT-1069 > Project: Apache Fineract > Issue Type: Bug >Reporter: Petri Tuomola >Priority: Major > > It seems that the calculation to determine expected interest in > RecurringDepositTest / FixedDepositTest breaks on 1st day of (each or some?) > months: seems that the logic calculates one day too much interest, and hence > the tests fail. This can be reproduced by setting system time to e.g. 1st > July and running the tests. This should be fixed as otherwise the builds will > always fail on this once a month. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-27) Rescheduling Repayments that fall On Holidays, to a period of 30 days
[ https://issues.apache.org/jira/browse/FINERACT-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-27: --- Assignee: Yemdjih Kaze Nasser > Rescheduling Repayments that fall On Holidays, to a period of 30 days > - > > Key: FINERACT-27 > URL: https://issues.apache.org/jira/browse/FINERACT-27 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Dayna Harp >Assignee: Yemdjih Kaze Nasser >Priority: Major > > https://mifosforge.jira.com/browse/MIFOSX-2439 > I have a concern that is really an inconvenience to our clients on Mifos > concerning the Holiday functionality. > REPRO STEPS > 1. go to Admin Tab >Organization >Manage Holidays >Create Holiday > 2. enter the Holiday parameters: > .Name*, From date*,To date* ,Repayment scheduled to* ,Description etc > PREFERRED OUTCOME: > 3: Our preferred scenario is to be able to reschedule the repayment > date for instance in the next 30 days (Conducive for > organizations where repayments are made on a monthly) > OUTCOME: > Error: Repayments rescheduled to date must be within 7 days before or > after from date and to date respectively. > REQUIRED: > Our recommendation is to have the above 7 day restriction increased to > about 30 days. > Please Advise on how soon this amendments can be implemented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-503) loan product missing after creation
[ https://issues.apache.org/jira/browse/FINERACT-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser closed FINERACT-503. Assignee: Yemdjih Kaze Nasser Resolution: Works for Me > loan product missing after creation > --- > > Key: FINERACT-503 > URL: https://issues.apache.org/jira/browse/FINERACT-503 > Project: Apache Fineract > Issue Type: Bug > Components: Loan > Environment: ubuntu > fineract 16.12.01 >Reporter: Kevin >Assignee: Yemdjih Kaze Nasser >Priority: Major > Attachments: missing-loanproduct.jpg > > > After creating a Loan Product, It doesn't appear on loan product listings > page. > please see the attachment. > However when you query the platform directly e.g. > https://SERVERIP:8443/fineract-provider/api/v1/loanproducts/2?tenantIdentifier=default=true > the loan product details exist. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1260) EntityExistsException: Cannot delete or update a parent row: a foreign key constraint fails (`fineract_default`.`m_loan_transaction_repayment_schedule_mapping`, CONS
[
https://issues.apache.org/jira/browse/FINERACT-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239067#comment-17239067
]
Yemdjih Kaze Nasser commented on FINERACT-1260:
---
I wish the logs could say a little more. Could really help in resolving this
issue.
> EntityExistsException: Cannot delete or update a parent row: a foreign key
> constraint fails
> (`fineract_default`.`m_loan_transaction_repayment_schedule_mapping`,
> CONSTRAINT `FK_mappings_m_loan_repayment_schedule`...
> --
>
> Key: FINERACT-1260
> URL: https://issues.apache.org/jira/browse/FINERACT-1260
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Michael Vorburger
>Priority: Blocker
>
> See FINERACT-932 for general background; I've found this in logs of
> [https://www.fineract.dev:|https://www.fineract.dev/]
> {code:java}
> Caused by: org.apache.openjpa.persistence.EntityExistsException: The
> transaction has been rolled back. See the nested exceptions for details on
> the errors that occurred. at
> org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2470)
> ~[openjpa-3.1.2.jar:3.1.2] at
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2308)
> ~[openjpa-3.1.2.jar:3.1.2] at
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:2199)
> ~[openjpa-3.1.2.jar:3.1.2] at
> org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:2116)
> ~[openjpa-3.1.2.jar:3.1.2] at
> org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:84)
> ~[openjpa-3.1.2.jar:3.1.2] at
> org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1600)
> ~[openjpa-3.1.2.jar:3.1.2] at
> org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:1035)
> ~[openjpa-3.1.2.jar:3.1.2] at
> org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:669)
> ~[openjpa-3.1.2.jar:3.1.2] at
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:534)
> ~[spring-orm-5.2.10.RELEASE.jar:5.2.10.RELEASE] ... 19 common frames omitted
> Caused by: org.apache.openjpa.persistence.EntityExistsException: Cannot
> delete or update a parent row: a foreign key constraint fails
> (`fineract_default`.`m_loan_transaction_repayment_schedule_mapping`,
> CONSTRAINT `FK_mappings_m_loan_repayment_schedule` FOREIGN KEY
> (`loan_repayment_schedule_id`) REFERENCES `m_loan_repayment_s){code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINCN-193) bring fineract-cn-interoperation up to date with other micro services
[ https://issues.apache.org/jira/browse/FINCN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINCN-193: -- Labels: outreachy2020 (was: ) > bring fineract-cn-interoperation up to date with other micro services > - > > Key: FINCN-193 > URL: https://issues.apache.org/jira/browse/FINCN-193 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Juhan Aasaru >Priority: Major > Labels: outreachy2020 > > fineract-cn-interoperation is missing changes that have been applied to other > micro services. These are: > # build with Travis-ci and add artifacts to artifactory > # switch MariaDB to Postgres > # switch Hibernate to EclipseLink > # create d multi-stage-docker build > # update gradle to 4.10.3 > # [FINCN-183 send our full url to > eureka|https://github.com/apache/fineract-cn-notifications/commit/67ae16ad8cda91bcf392d48ba362de8c4a9dd09c] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINCN-186) Research upgrading to Java 11
[ https://issues.apache.org/jira/browse/FINCN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINCN-186: -- Labels: outreachy2020 (was: ) > Research upgrading to Java 11 > - > > Key: FINCN-186 > URL: https://issues.apache.org/jira/browse/FINCN-186 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Juhan Aasaru >Priority: Major > Labels: outreachy2020 > > Fineract-CN works on Java 8 and eventually the support will be discontinued. > Next Long Term Support (LTS) version is Java 11. > Also we could benefit from the module system introduced by Java 9 - running > apps on module system would require less memory (since we don't need all the > modules of Java). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINCN-240) Use a bot to automate dependency updates
Yemdjih Kaze Nasser created FINCN-240: - Summary: Use a bot to automate dependency updates Key: FINCN-240 URL: https://issues.apache.org/jira/browse/FINCN-240 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Yemdjih Kaze Nasser To save a lot of time and make sure that packages are updated frequently, it would be good to have a bot such as renovate bot (as we have in Fineract 1.x) or any other bot handle this so the they can just be reviewed and merged when needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-172) Upgrade all fineract-cn-* apps to latest Spring Boot / Spring Framework
[ https://issues.apache.org/jira/browse/FINCN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINCN-172: - Assignee: (was: Saransh Sharma) > Upgrade all fineract-cn-* apps to latest Spring Boot / Spring Framework > --- > > Key: FINCN-172 > URL: https://issues.apache.org/jira/browse/FINCN-172 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Juhan Aasaru >Priority: Major > Labels: outreachy2020 > Time Spent: 0.5h > Remaining Estimate: 0h > > Proposed by [~Kwesi] : > 1. Upgrading Fineract CN from Spring Boot 1.4.1 to 2.1.+ > 2. Upgrading Fineract CN from Spring Framework from 4.3.3 to 5.1.+ > > This should be done in the same time to all fineract-cn-* applications > (similar to https://issues.apache.org/jira/browse/FINCN-170 ) - so one would > create pull requests for all apps and once the work is accepted all pull > requests would be merged together. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINCN-172) Upgrade all fineract-cn-* apps to latest Spring Boot / Spring Framework
[ https://issues.apache.org/jira/browse/FINCN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINCN-172: -- Labels: outreachy2020 (was: ) > Upgrade all fineract-cn-* apps to latest Spring Boot / Spring Framework > --- > > Key: FINCN-172 > URL: https://issues.apache.org/jira/browse/FINCN-172 > Project: Fineract Cloud Native > Issue Type: Improvement >Reporter: Juhan Aasaru >Assignee: Saransh Sharma >Priority: Major > Labels: outreachy2020 > Time Spent: 0.5h > Remaining Estimate: 0h > > Proposed by [~Kwesi] : > 1. Upgrading Fineract CN from Spring Boot 1.4.1 to 2.1.+ > 2. Upgrading Fineract CN from Spring Framework from 4.3.3 to 5.1.+ > > This should be done in the same time to all fineract-cn-* applications > (similar to https://issues.apache.org/jira/browse/FINCN-170 ) - so one would > create pull requests for all apps and once the work is accepted all pull > requests would be merged together. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINCN-110) Place `google()` repository as the first priority repository
[
https://issues.apache.org/jira/browse/FINCN-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser updated FINCN-110:
--
Labels: Gradle beginner outreachy2020 (was: Gradle beginner)
> Place `google()` repository as the first priority repository
>
>
> Key: FINCN-110
> URL: https://issues.apache.org/jira/browse/FINCN-110
> Project: Fineract Cloud Native
> Issue Type: Improvement
> Components: fineract-cn-mobile
> Environment: Ubuntu 18.04.1
> Android Studio 3.2.1
>Reporter: Dundi Raja Vamsi Reddy
>Priority: Minor
> Labels: Gradle, beginner, outreachy2020
>
> In project level build. gradle file jcenter() repository have first priority
> than google() repository. My idea is to Place {{google()}} repository as the
> first priority repository to avoid such errors in the future like
> *Failed to resolve: multidex-instrumentation*
> Here is the link to check to solve this error
> [https://stackoverflow.com/questions/45608362/android-studio-3-0-beta-1-failed-to-resolve-com-android-supportmultidex1-0-2|https://github.com/amahi/android/issues/here]
> In our project
> [here|https://github.com/apache/fineract-cn-mobile/blob/development/build.gradle#L20]
> google must be placed as a first priority.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINCN-60) Update Readme
[ https://issues.apache.org/jira/browse/FINCN-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINCN-60: - Labels: outreachy2020 (was: ) > Update Readme > - > > Key: FINCN-60 > URL: https://issues.apache.org/jira/browse/FINCN-60 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-mobile >Reporter: Dilpreet Singh >Priority: Minor > Labels: outreachy2020 > > ReadMe.md does not have proper infromation.Actually for a begginer to start > with it is very difficult to understand the project. So it is requirede to > update readme file > Steps to reproduce: > will gather the required and additional information from Various Sources and > write it in readme in a proper manner > provide link to dummy login id > paste screenshot for app -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-982) Completely ditch use of Drizzle JDBC Driver after all
[ https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205986#comment-17205986 ] Yemdjih Kaze Nasser commented on FINERACT-982: -- (y) > Completely ditch use of Drizzle JDBC Driver after all > - > > Key: FINERACT-982 > URL: https://issues.apache.org/jira/browse/FINERACT-982 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: scalability > > Fineract's use of the un-maintained Drizzle JDBC driver continues to cause > confusion and pains like FINERACT-980, and note e.g. the proposed removal of > the alternative MySQL JDBC driver in > [https://github.com/apache/fineract/pull/887.] > Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and > LEGAL-462. > LEGAL-462 has clarified that the Fineract ZIP distribution must include > Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and > currently (given the confusion in FINERACT-980 apparently do?!) use it for > tests. > What if to reduce variability we just removed that old Drizzle JDBC driver > after all? We could run our tests using (preferably) the very well maintained > MariaDB JDBC driver client (the actual DB server is a totally separate > discussion, see FINERACT-896). We would (have to) distribute the ZIP for > download without a JDBC driver, and just some documentation inviting users to > DL and add one. > But the exact situation about distributing in a Docker container image isn't > clear, to me... > FYI [~awasum], [~ptuomola], [~xurror] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-982) Completely ditch use of Drizzle JDBC Driver after all
[ https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205765#comment-17205765 ] Yemdjih Kaze Nasser commented on FINERACT-982: -- This is a good place where we could leverage multiple application profiles. I suggest we reinstate the production and development profiles separation. I could look into that. > Completely ditch use of Drizzle JDBC Driver after all > - > > Key: FINERACT-982 > URL: https://issues.apache.org/jira/browse/FINERACT-982 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: scalability > > Fineract's use of the un-maintained Drizzle JDBC driver continues to cause > confusion and pains like FINERACT-980, and note e.g. the proposed removal of > the alternative MySQL JDBC driver in > [https://github.com/apache/fineract/pull/887.] > Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and > LEGAL-462. > LEGAL-462 has clarified that the Fineract ZIP distribution must include > Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and > currently (given the confusion in FINERACT-980 apparently do?!) use it for > tests. > What if to reduce variability we just removed that old Drizzle JDBC driver > after all? We could run our tests using (preferably) the very well maintained > MariaDB JDBC driver client (the actual DB server is a totally separate > discussion, see FINERACT-896). We would (have to) distribute the ZIP for > download without a JDBC driver, and just some documentation inviting users to > DL and add one. > But the exact situation about distributing in a Docker container image isn't > clear, to me... > FYI [~awasum], [~ptuomola], [~xurror] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-982) Completely ditch use of Drizzle JDBC Driver after all
[ https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-982: Assignee: Yemdjih Kaze Nasser > Completely ditch use of Drizzle JDBC Driver after all > - > > Key: FINERACT-982 > URL: https://issues.apache.org/jira/browse/FINERACT-982 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: scalability > > Fineract's use of the un-maintained Drizzle JDBC driver continues to cause > confusion and pains like FINERACT-980, and note e.g. the proposed removal of > the alternative MySQL JDBC driver in > [https://github.com/apache/fineract/pull/887.] > Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and > LEGAL-462. > LEGAL-462 has clarified that the Fineract ZIP distribution must include > Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and > currently (given the confusion in FINERACT-980 apparently do?!) use it for > tests. > What if to reduce variability we just removed that old Drizzle JDBC driver > after all? We could run our tests using (preferably) the very well maintained > MariaDB JDBC driver client (the actual DB server is a totally separate > discussion, see FINERACT-896). We would (have to) distribute the ZIP for > download without a JDBC driver, and just some documentation inviting users to > DL and add one. > But the exact situation about distributing in a Docker container image isn't > clear, to me... > FYI [~awasum], [~ptuomola], [~xurror] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1140) Adopt GenerationType.TABLE as ID generation strategy
[ https://issues.apache.org/jira/browse/FINERACT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1140: - Assignee: Yemdjih Kaze Nasser > Adopt GenerationType.TABLE as ID generation strategy > > > Key: FINERACT-1140 > URL: https://issues.apache.org/jira/browse/FINERACT-1140 > Project: Apache Fineract > Issue Type: Test >Affects Versions: 1.5.0 >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Working with eclipselink, I noticed there were situations where when trying > to persist objects with sub entities, the IDs of the sub entities where not > generated fast enough making the ID column to always be set to null causing a > lot SQLIntegrityViolations. > As a solution of last resort I experimented with table generation strategy > which is able to set ID upon object creation instead of at persist time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1140) Adopt GenerationType.TABLE as ID generation strategy
Yemdjih Kaze Nasser created FINERACT-1140: - Summary: Adopt GenerationType.TABLE as ID generation strategy Key: FINERACT-1140 URL: https://issues.apache.org/jira/browse/FINERACT-1140 Project: Apache Fineract Issue Type: Test Affects Versions: 1.5.0 Reporter: Yemdjih Kaze Nasser Working with eclipselink, I noticed there were situations where when trying to persist objects with sub entities, the IDs of the sub entities where not generated fast enough making the ID column to always be set to null causing a lot SQLIntegrityViolations. As a solution of last resort I experimented with table generation strategy which is able to set ID upon object creation instead of at persist time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1128) Travis build fails with connection refused
[
https://issues.apache.org/jira/browse/FINERACT-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser resolved FINERACT-1128.
---
Fix Version/s: 1.4.0
Resolution: Fixed
> Travis build fails with connection refused
> --
>
> Key: FINERACT-1128
> URL: https://issues.apache.org/jira/browse/FINERACT-1128
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Petri Tuomola
>Assignee: Petri Tuomola
>Priority: Major
> Fix For: 1.4.0
>
>
> Travis build often fails with the following error when trying to check that
> the Docker container has come up as expected:
> http: error: ConnectionError: HTTPSConnectionPool(host='localhost',
> port=8443): Max retries exceeded with url: /fineract-provider/actuator/health
> (Caused by NewConnectionError(' object at 0x7fd6051a9c18>: Failed to establish a new connection: [Errno 111]
> Connection refused',)) while doing GET request to URL:
> [https://localhost:8443/fineract-provider/actuator/health]
> Retrying the build works so this is an issue with infra rather than code -
> may just be due to the Docker container taking longer than expected in coming
> up?
> One possible solution could be to switch from http to curl and then use
> curl's facility for retries - i.e. try the connection 5 times with 30 second
> breaks between retries to see if the container comes up.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1103) Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
[
https://issues.apache.org/jira/browse/FINERACT-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17185353#comment-17185353
]
Yemdjih Kaze Nasser commented on FINERACT-1103:
---
(y)
> Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
> --
>
> Key: FINERACT-1103
> URL: https://issues.apache.org/jira/browse/FINERACT-1103
> Project: Apache Fineract
> Issue Type: Sub-task
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Assignee: Yemdjih Kaze Nasser
>Priority: Blocker
> Fix For: 1.4.0
>
>
> {code:java}
> Caused by: org.eclipse.persistence.exceptions.IntegrityException:
> Descriptor Exceptions:
> -
>
> Exception [EclipseLink-93] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DescriptorException
> Exception Description: The table [m_organisation_creditbureau] is not present
> in this descriptor.
> Descriptor:
> RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
> --> [DatabaseTable(m_creditbureau)])
>
> Exception [EclipseLink-41] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DescriptorException
> Exception Description: A non-read-only mapping must be defined for the
> sequence number field.
> Descriptor:
> RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
> --> [DatabaseTable(m_creditbureau)]){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1103) Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
[
https://issues.apache.org/jira/browse/FINERACT-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17184940#comment-17184940
]
Yemdjih Kaze Nasser commented on FINERACT-1103:
---
Dropping that is fine cause the column exists on the other side of the
relationship.
> Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
> --
>
> Key: FINERACT-1103
> URL: https://issues.apache.org/jira/browse/FINERACT-1103
> Project: Apache Fineract
> Issue Type: Sub-task
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Assignee: Yemdjih Kaze Nasser
>Priority: Blocker
> Fix For: 1.4.0
>
>
> {code:java}
> Caused by: org.eclipse.persistence.exceptions.IntegrityException:
> Descriptor Exceptions:
> -
>
> Exception [EclipseLink-93] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DescriptorException
> Exception Description: The table [m_organisation_creditbureau] is not present
> in this descriptor.
> Descriptor:
> RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
> --> [DatabaseTable(m_creditbureau)])
>
> Exception [EclipseLink-41] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DescriptorException
> Exception Description: A non-read-only mapping must be defined for the
> sequence number field.
> Descriptor:
> RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
> --> [DatabaseTable(m_creditbureau)]){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-1105) Swagger generates invalid Open API Specification file
[
https://issues.apache.org/jira/browse/FINERACT-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser resolved FINERACT-1105.
---
Fix Version/s: 1.4.0
Resolution: Fixed
> Swagger generates invalid Open API Specification file
> -
>
> Key: FINERACT-1105
> URL: https://issues.apache.org/jira/browse/FINERACT-1105
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Chinmay Kulkarni
>Assignee: Chinmay Kulkarni
>Priority: Minor
> Fix For: 1.4.0
>
>
> The Open API Specification file produced by Swagger Gradle Plugin is invalid.
> # Run *./gradlew build*
> # Use the contents of the generated Open API Spec file
> *build/classes/java/main/static/swagger-ui/fineract.yaml* to debug/validate
> spec file from here: [https://validator.swagger.io/] - Use Debug POST
> request to validate
> The validator returns the following:
> {code:yaml}
> ---
> messages: - "attribute paths.'/glclosures'(get).responses.200.description is
> missing"
> - "attribute paths.'/glclosures'(post).responses.200.description is missing"
> - "attribute paths.'/glclosures/{glClosureId}'(get).responses.200.description
> is missing"
> - "attribute paths.'/glclosures/{glClosureId}'(put).responses.200.description
> is missing"
> - "attribute
> paths.'/glclosures/{glClosureId}'(delete).responses.200.description is\
> \ missing"
> - "attribute
> paths.'/financialactivityaccounts'(get).responses.200.description is\
> \ missing"
> - "attribute
> paths.'/financialactivityaccounts'(post).responses.200.description is\
> \ missing"
> - "attribute
> paths.'/financialactivityaccounts/{mappingId}'(get).responses.200.description\
> \ is missing"
> - "attribute
> paths.'/financialactivityaccounts/{mappingId}'(put).responses.200.description\
> \ is missing"
> - "attribute paths.'/glaccounts/template'(get).responses.200.description is
> missing"
> - "attribute paths.'/glaccounts'(get).responses.200.description is missing"
> - "attribute paths.'/glaccounts'(post).responses.200.description is missing"
> - "attribute paths.'/glaccounts/{glAccountId}'(get).responses.200.description
> is missing"
> - "attribute paths.'/glaccounts/{glAccountId}'(put).responses.200.description
> is missing"
> - "attribute
> paths.'/glaccounts/{glAccountId}'(delete).responses.200.description is\
> \ missing"
> - "attribute
> paths.'/journalentries/{transactionId}'(post).responses.200.description\
> \ is missing"
> - "attribute
> paths.'/journalentries/{journalEntryId}'(get).responses.200.description\
> \ is missing"
> - "attribute paths.'/journalentries'(get).responses.200.description is
> missing"
> - "attribute paths.'/journalentries'(post).responses.200.description is
> missing"
> - "attribute paths.'/provisioningentries'(get).responses.200.description is
> missing"
> - "attribute paths.'/provisioningentries'(post).responses.200.description is
> missing"
> - "attribute
> paths.'/provisioningentries/entries'(get).responses.200.description is\
> \ missing"
> - "attribute
> paths.'/provisioningentries/{entryId}'(get).responses.200.description\
> \ is missing"
> - "attribute
> paths.'/provisioningentries/{entryId}'(post).responses.200.description\
> \ is missing"
> - "attribute paths.'/accountingrules'(get).responses.200.description is
> missing"
> - "attribute paths.'/accountingrules'(post).responses.200.description is
> missing"
> - "attribute
> paths.'/accountingrules/{accountingRuleId}'(get).responses.200.description\
> \ is missing"
> - "attribute
> paths.'/accountingrules/{accountingRuleId}'(put).responses.200.description\
> \ is missing"
> - "attribute
> paths.'/accountingrules/{accountingRuleId}'(delete).responses.200.description\
> \ is missing"
> - "attribute paths.'/accountingrules/template'(get).responses.200.description
> is missing"
> - "attribute paths.'/audits/searchtemplate'(get).responses.200.description is
> missing"
> - "attribute paths.'/audits'(get).responses.200.description is missing"
> - "attribute paths.'/audits/{auditId}'(get).responses.200.description is
> missing"
> - "attribute
> paths.'/makercheckers/searchtemplate'(get).responses.200.description\
> \ is missing"
> - "attribute paths.'/makercheckers/{auditId}'(post).responses.200.description
> is missing"
> - "attribute
> paths.'/makercheckers/{auditId}'(delete).responses.200.description is\
> \ missing"
> - "attribute paths.'/makercheckers'(get).responses.200.description is missing"
> - "attribute paths.'/accountnumberformats'(get).responses.200.description is
> missing"
> - "attribute paths.'/accountnumberformats'(post).responses.200.description is
> missing"
> - "attribute
> paths.'/accountnumberformats/template'(get).responses.200.description\
> \ is missing"
> - "attribute
[jira] [Created] (FINERACT-1126) ClientLoanIntegrationTest > Internal Exception: java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '1126' for key 'PRIMARY'
Yemdjih Kaze Nasser created FINERACT-1126:
-
Summary: ClientLoanIntegrationTest > Internal Exception:
java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '1126' for
key 'PRIMARY'
Key: FINERACT-1126
URL: https://issues.apache.org/jira/browse/FINERACT-1126
Project: Apache Fineract
Issue Type: Bug
Affects Versions: 1.5.0
Reporter: Yemdjih Kaze Nasser
{code:java}
Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.7.7.v20200504-69f2c2b80d):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
Duplicate entry '1126' for key 'PRIMARY'
Error Code: 1062
Call: INSERT INTO m_loan_repayment_schedule (ID, created_date, duedate,
accrual_fee_charges_derived, fee_charges_amount, fee_charges_completed_derived,
fee_charges_w
aived_derived, fee_charges_writtenoff_derived, fromdate, installment,
accrual_interest_derived, interest_amount, interest_completed_derived,
interest_waived_derived,
interest_writtenoff_derived, lastmodified_date, completed_derived,
obligations_met_on_date, accrual_penalty_charges_derived,
penalty_charges_amount, penalty_charges
_completed_derived, penalty_charges_waived_derived,
penalty_charges_writtenoff_derived, principal_amount,
principal_completed_derived, principal_writtenoff_derived,
recalculated_interest_component, total_paid_in_advance_derived,
total_paid_late_derived, createdby_id, lastmodifiedby_id, loan_id) VALUES (?,
?, ?, ?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [1126, 2020-08-22 06:46:13.449, 2020-08-22, null, 3.47, 3.47,
null, null, 2020-08-15, 2, null, 34.69, 34.69, null, null, 2020-08-22
06:46:13.449, tru
e, 2020-08-22, null, null, null, null, null, 7517.24, 7517.24, null, false,
4000.00, null, 1, 1, 91]
Query:
InsertObjectQuery(org.apache.fineract.portfolio.loanaccount.domain.LoanTransactionToRepaymentScheduleMapping@53d244d6)
at
org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:333)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:908)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:970)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:640)
at
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:151)
at
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:
136)
at
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:84)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:612)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:567)
at
org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2099)
at
org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:313)
at
org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:277)
at
org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:263)
at
org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:413)
at
org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:167)
at
org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:182)
at
org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:504)
at
org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:82)
at
org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWrite(DatabaseQueryMechanism.java:261)
at
org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:62)
at
org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:911)
at
org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:810)
at
[jira] [Resolved] (FINERACT-1048) SchedulerJob executeAndAwait predicate returns false with successful transaction
[ https://issues.apache.org/jira/browse/FINERACT-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-1048. --- Fix Version/s: 1.5.0 Assignee: Yemdjih Kaze Nasser Resolution: Fixed > SchedulerJob executeAndAwait predicate returns false with successful > transaction > > > Key: FINERACT-1048 > URL: https://issues.apache.org/jira/browse/FINERACT-1048 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > Fix For: 1.5.0 > > > Schedularjob acting crazy again. Time execution time comparison is faulty in > tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1118) Don't run Swagger code generation if previous build steps failed
[ https://issues.apache.org/jira/browse/FINERACT-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-1118. --- Resolution: Fixed > Don't run Swagger code generation if previous build steps failed > > > Key: FINERACT-1118 > URL: https://issues.apache.org/jira/browse/FINERACT-1118 > Project: Apache Fineract > Issue Type: Bug > Components: Build >Reporter: Petri Tuomola >Assignee: Petri Tuomola >Priority: Minor > Fix For: 1.4.0 > > > Currently swagger code generation runs even if the build steps has failed - > which makes it confusing to see what actually was the original / first > failure. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1118) Don't run Swagger code generation if previous build steps failed
[ https://issues.apache.org/jira/browse/FINERACT-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINERACT-1118: -- Fix Version/s: 1.4.0 > Don't run Swagger code generation if previous build steps failed > > > Key: FINERACT-1118 > URL: https://issues.apache.org/jira/browse/FINERACT-1118 > Project: Apache Fineract > Issue Type: Bug > Components: Build >Reporter: Petri Tuomola >Assignee: Petri Tuomola >Priority: Minor > Fix For: 1.4.0 > > > Currently swagger code generation runs even if the build steps has failed - > which makes it confusing to see what actually was the original / first > failure. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-897) Make Fineract compatible with both MySQL5.7 and MySQL 8
[ https://issues.apache.org/jira/browse/FINERACT-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17175599#comment-17175599 ] Yemdjih Kaze Nasser edited comment on FINERACT-897 at 8/11/20, 2:16 PM: Also, there is a license break with mysql connectorj which uses GPL license since we could not have mysql v8 to work with drizzle driver. Check [https://www.apache.org/licenses/GPL-compatibility.html] I think the way forward from here to ensure the support of both mysql v5 and v8 is to do as [~vorburger] suggested and have it tested in the travis CI. With this check, once the project is released, users can simply change the driver and will be good to work with mysql v8 was (Author: kaze): Also, there is a license break with mysql connectorj which uses GPL license since we could not have mysql v8 to work with drizzle driver. Check [https://www.apache.org/licenses/GPL-compatibility.html] > Make Fineract compatible with both MySQL5.7 and MySQL 8 > --- > > Key: FINERACT-897 > URL: https://issues.apache.org/jira/browse/FINERACT-897 > Project: Apache Fineract > Issue Type: New Feature > Components: Database >Reporter: Michael Vorburger >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: technical > Fix For: 1.4.0 > > > Test Fineract with the latest version of MySQL v8 instead of the old MySQL 5 > we currently seem to be mostly using. > Hopefully our use of the (very old...) Drizzle JDBC driver doesn't cause any > issues for this; if it does, note FINERACT-762. > See also FINERACT-896. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-897) Make Fineract compatible with both MySQL5.7 and MySQL 8
[ https://issues.apache.org/jira/browse/FINERACT-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17175599#comment-17175599 ] Yemdjih Kaze Nasser commented on FINERACT-897: -- Also, there is a license break with mysql connectorj which uses GPL license since we could not have mysql v8 to work with drizzle driver. Check [https://www.apache.org/licenses/GPL-compatibility.html] > Make Fineract compatible with both MySQL5.7 and MySQL 8 > --- > > Key: FINERACT-897 > URL: https://issues.apache.org/jira/browse/FINERACT-897 > Project: Apache Fineract > Issue Type: New Feature > Components: Database >Reporter: Michael Vorburger >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: technical > Fix For: 1.4.0 > > > Test Fineract with the latest version of MySQL v8 instead of the old MySQL 5 > we currently seem to be mostly using. > Hopefully our use of the (very old...) Drizzle JDBC driver doesn't cause any > issues for this; if it does, note FINERACT-762. > See also FINERACT-896. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1104) Adjust JPQL query in likelihood repository
[
https://issues.apache.org/jira/browse/FINERACT-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser resolved FINERACT-1104.
---
Resolution: Fixed
> Adjust JPQL query in likelihood repository
> --
>
> Key: FINERACT-1104
> URL: https://issues.apache.org/jira/browse/FINERACT-1104
> Project: Apache Fineract
> Issue Type: Sub-task
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Assignee: Yemdjih Kaze Nasser
>Priority: Blocker
>
> {code:java}
> Caused by: org.eclipse.persistence.exceptions.JPQLException:
> Exception Description: Problem compiling [select liklihood FROM Likelihood
> liklihood WHERE ppi_name =:ppiName AND id <>:id].
> [49, 57] The identification variable 'ppi_name' is not defined in the FROM
> clause.
> [73, 75] The identification variable 'id' is not defined in the FROM clause.
> at
> org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildException(HermesParser.java:157)
> ~[org.eclipse.persistence.core-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.jpql.HermesParser.validate(HermesParser.java:349)
> ~[org.eclipse.persistence.core-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.jpql.HermesParser.populateQueryImp(HermesParser.java:280)
> ~[org.eclipse.persistence.core-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildQuery(HermesParser.java:165)
> ~[org.eclipse.persistence.core-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:142)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:118)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.(EJBQueryImpl.java:104)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.(EJBQueryImpl.java:88)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.createQuery(EntityManagerImpl.java:1749)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FINERACT-1103) Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
[
https://issues.apache.org/jira/browse/FINERACT-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser resolved FINERACT-1103.
---
Resolution: Fixed
> Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
> --
>
> Key: FINERACT-1103
> URL: https://issues.apache.org/jira/browse/FINERACT-1103
> Project: Apache Fineract
> Issue Type: Sub-task
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Assignee: Yemdjih Kaze Nasser
>Priority: Blocker
>
> {code:java}
> Caused by: org.eclipse.persistence.exceptions.IntegrityException:
> Descriptor Exceptions:
> -
>
> Exception [EclipseLink-93] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DescriptorException
> Exception Description: The table [m_organisation_creditbureau] is not present
> in this descriptor.
> Descriptor:
> RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
> --> [DatabaseTable(m_creditbureau)])
>
> Exception [EclipseLink-41] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DescriptorException
> Exception Description: A non-read-only mapping must be defined for the
> sequence number field.
> Descriptor:
> RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
> --> [DatabaseTable(m_creditbureau)]){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FINERACT-1077) Migrate from legacy plugins applications to plugins DSL in build.gradle
[ https://issues.apache.org/jira/browse/FINERACT-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1077: - Assignee: (was: Yemdjih Kaze Nasser) > Migrate from legacy plugins applications to plugins DSL in build.gradle > --- > > Key: FINERACT-1077 > URL: https://issues.apache.org/jira/browse/FINERACT-1077 > Project: Apache Fineract > Issue Type: Improvement > Components: Build >Affects Versions: 1.4.0 >Reporter: Yemdjih Kaze Nasser >Priority: Major > > We are still using the old way of applying gradle plugins in our > build.gradle. Today there is more convenient way of doing this which more and > more packages are using. This would make the build less cumbersome too and > plugins easier to maintain and apply. > [https://docs.gradle.org/current/userguide/plugins.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1104) Adjust JPQL query in likelihood repository
[
https://issues.apache.org/jira/browse/FINERACT-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser reassigned FINERACT-1104:
-
Assignee: Yemdjih Kaze Nasser
> Adjust JPQL query in likelihood repository
> --
>
> Key: FINERACT-1104
> URL: https://issues.apache.org/jira/browse/FINERACT-1104
> Project: Apache Fineract
> Issue Type: Sub-task
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Assignee: Yemdjih Kaze Nasser
>Priority: Blocker
>
> {code:java}
> Caused by: org.eclipse.persistence.exceptions.JPQLException:
> Exception Description: Problem compiling [select liklihood FROM Likelihood
> liklihood WHERE ppi_name =:ppiName AND id <>:id].
> [49, 57] The identification variable 'ppi_name' is not defined in the FROM
> clause.
> [73, 75] The identification variable 'id' is not defined in the FROM clause.
> at
> org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildException(HermesParser.java:157)
> ~[org.eclipse.persistence.core-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.jpql.HermesParser.validate(HermesParser.java:349)
> ~[org.eclipse.persistence.core-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.jpql.HermesParser.populateQueryImp(HermesParser.java:280)
> ~[org.eclipse.persistence.core-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildQuery(HermesParser.java:165)
> ~[org.eclipse.persistence.core-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:142)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:118)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.(EJBQueryImpl.java:104)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EJBQueryImpl.(EJBQueryImpl.java:88)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.createQuery(EntityManagerImpl.java:1749)
> ~[org.eclipse.persistence.jpa-2.7.7.jar:na]{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FINERACT-1103) Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
[
https://issues.apache.org/jira/browse/FINERACT-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser reassigned FINERACT-1103:
-
Assignee: Yemdjih Kaze Nasser
> Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
> --
>
> Key: FINERACT-1103
> URL: https://issues.apache.org/jira/browse/FINERACT-1103
> Project: Apache Fineract
> Issue Type: Sub-task
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Assignee: Yemdjih Kaze Nasser
>Priority: Blocker
>
> {code:java}
> Caused by: org.eclipse.persistence.exceptions.IntegrityException:
> Descriptor Exceptions:
> -
>
> Exception [EclipseLink-93] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DescriptorException
> Exception Description: The table [m_organisation_creditbureau] is not present
> in this descriptor.
> Descriptor:
> RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
> --> [DatabaseTable(m_creditbureau)])
>
> Exception [EclipseLink-41] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DescriptorException
> Exception Description: A non-read-only mapping must be defined for the
> sequence number field.
> Descriptor:
> RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
> --> [DatabaseTable(m_creditbureau)]){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FINERACT-1104) Adjust JPQL query in likelihood repository
Yemdjih Kaze Nasser created FINERACT-1104:
-
Summary: Adjust JPQL query in likelihood repository
Key: FINERACT-1104
URL: https://issues.apache.org/jira/browse/FINERACT-1104
Project: Apache Fineract
Issue Type: Sub-task
Affects Versions: 1.4.0
Reporter: Yemdjih Kaze Nasser
{code:java}
Caused by: org.eclipse.persistence.exceptions.JPQLException:
Exception Description: Problem compiling [select liklihood FROM Likelihood
liklihood WHERE ppi_name =:ppiName AND id <>:id].
[49, 57] The identification variable 'ppi_name' is not defined in the FROM
clause.
[73, 75] The identification variable 'id' is not defined in the FROM clause.
at
org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildException(HermesParser.java:157)
~[org.eclipse.persistence.core-2.7.7.jar:na]
at
org.eclipse.persistence.internal.jpa.jpql.HermesParser.validate(HermesParser.java:349)
~[org.eclipse.persistence.core-2.7.7.jar:na]
at
org.eclipse.persistence.internal.jpa.jpql.HermesParser.populateQueryImp(HermesParser.java:280)
~[org.eclipse.persistence.core-2.7.7.jar:na]
at
org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildQuery(HermesParser.java:165)
~[org.eclipse.persistence.core-2.7.7.jar:na]
at
org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:142)
~[org.eclipse.persistence.jpa-2.7.7.jar:na]
at
org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:118)
~[org.eclipse.persistence.jpa-2.7.7.jar:na]
at
org.eclipse.persistence.internal.jpa.EJBQueryImpl.(EJBQueryImpl.java:104)
~[org.eclipse.persistence.jpa-2.7.7.jar:na]
at
org.eclipse.persistence.internal.jpa.EJBQueryImpl.(EJBQueryImpl.java:88)
~[org.eclipse.persistence.jpa-2.7.7.jar:na]
at
org.eclipse.persistence.internal.jpa.EntityManagerImpl.createQuery(EntityManagerImpl.java:1749)
~[org.eclipse.persistence.jpa-2.7.7.jar:na]{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FINERACT-1103) Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException
Yemdjih Kaze Nasser created FINERACT-1103:
-
Summary: Resolve
org.eclipse.persistence.exceptions.EntityManagerSetupException
Key: FINERACT-1103
URL: https://issues.apache.org/jira/browse/FINERACT-1103
Project: Apache Fineract
Issue Type: Sub-task
Affects Versions: 1.4.0
Reporter: Yemdjih Kaze Nasser
{code:java}
Caused by: org.eclipse.persistence.exceptions.IntegrityException:
Descriptor Exceptions:
-
Exception [EclipseLink-93] (Eclipse Persistence Services -
2.7.7.v20200504-69f2c2b80d):
org.eclipse.persistence.exceptions.DescriptorException
Exception Description: The table [m_organisation_creditbureau] is not present
in this descriptor.
Descriptor:
RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
--> [DatabaseTable(m_creditbureau)])
Exception [EclipseLink-41] (Eclipse Persistence Services -
2.7.7.v20200504-69f2c2b80d):
org.eclipse.persistence.exceptions.DescriptorException
Exception Description: A non-read-only mapping must be defined for the sequence
number field.
Descriptor:
RelationalDescriptor(org.apache.fineract.infrastructure.creditbureau.domain.CreditBureau
--> [DatabaseTable(m_creditbureau)]){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink
[ https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169307#comment-17169307 ] Yemdjih Kaze Nasser commented on FINERACT-849: -- Sounds good and rationale to me. I will open the PR against a new branch instead of develop. > Migrate Fineract ORM from OpenJPA to EclipseLink > > > Key: FINERACT-849 > URL: https://issues.apache.org/jira/browse/FINERACT-849 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ed Cable >Assignee: Yemdjih Kaze Nasser >Priority: Major > Labels: gsoc2020, hard, mentor, technical > Fix For: 1.5.0 > > > In line with the rationale for choosing EclipseLink as the ORM replacement > for Hibernate in FineractCN, we have broad consensus across the community to > swap out OpenJPA with EclipseLink. > OpenJPA seems to have reached its end of life with community activity > withering and the trade-offs between Hibernate and EclipseLink are much > lower. We also have community members who are migrating Fineract 1.x to > PostGreSQL and would benefit from the increased performance with EclipseLink. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1099) Failing FixedDepositTest > testFixedDepositAccountClosureTypeWithdrawal_WITH_HOLD_TAX
[
https://issues.apache.org/jira/browse/FINERACT-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169043#comment-17169043
]
Yemdjih Kaze Nasser commented on FINERACT-1099:
---
I will ignore this test case for now so other PRs can be merged.
> Failing FixedDepositTest >
> testFixedDepositAccountClosureTypeWithdrawal_WITH_HOLD_TAX
> -
>
> Key: FINERACT-1099
> URL: https://issues.apache.org/jira/browse/FINERACT-1099
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Priority: Major
>
> This has been happening a couple of times, from my local work branches to
> renovate bot updates. I think it's fair that it comes here
> {code:java}
> FixedDepositTest >
> testFixedDepositAccountClosureTypeWithdrawal_WITH_HOLD_TAX() FAILED459
> org.opentest4j.AssertionFailedError: Journal Entry not found ==> expected:
> but was: 460at
> org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)461
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:40)462
> at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:193)463
> at
> org.apache.fineract.integrationtests.common.accounting.JournalEntryHelper.checkJournalEntry(JournalEntryHelper.java:82)464
> at
> org.apache.fineract.integrationtests.common.accounting.JournalEntryHelper.checkJournalEntryForLiabilityAccount(JournalEntryHelper.java:55)465
> at
> org.apache.fineract.integrationtests.FixedDepositTest.testFixedDepositAccountClosureTypeWithdrawal_WITH_HOLD_TAX(FixedDepositTest.java:518)
> {code}
> FYI: [~awasum], [~vorburger], [~ptuomola]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FINERACT-1099) Failing FixedDepositTest > testFixedDepositAccountClosureTypeWithdrawal_WITH_HOLD_TAX
Yemdjih Kaze Nasser created FINERACT-1099:
-
Summary: Failing FixedDepositTest >
testFixedDepositAccountClosureTypeWithdrawal_WITH_HOLD_TAX
Key: FINERACT-1099
URL: https://issues.apache.org/jira/browse/FINERACT-1099
Project: Apache Fineract
Issue Type: Bug
Affects Versions: 1.4.0
Reporter: Yemdjih Kaze Nasser
This has been happening a couple of times, from my local work branches to
renovate bot updates. I think it's fair that it comes here
{code:java}
FixedDepositTest > testFixedDepositAccountClosureTypeWithdrawal_WITH_HOLD_TAX()
FAILED459org.opentest4j.AssertionFailedError: Journal Entry not found ==>
expected: but was: 460at
org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)461at
org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:40)462at
org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:193)463at
org.apache.fineract.integrationtests.common.accounting.JournalEntryHelper.checkJournalEntry(JournalEntryHelper.java:82)464
at
org.apache.fineract.integrationtests.common.accounting.JournalEntryHelper.checkJournalEntryForLiabilityAccount(JournalEntryHelper.java:55)465
at
org.apache.fineract.integrationtests.FixedDepositTest.testFixedDepositAccountClosureTypeWithdrawal_WITH_HOLD_TAX(FixedDepositTest.java:518)
{code}
FYI: [~awasum], [~vorburger], [~ptuomola]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FINERACT-1098) Add JpaSystemException as a JPA transaction exception
[ https://issues.apache.org/jira/browse/FINERACT-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1098: - Assignee: Yemdjih Kaze Nasser > Add JpaSystemException as a JPA transaction exception > - > > Key: FINERACT-1098 > URL: https://issues.apache.org/jira/browse/FINERACT-1098 > Project: Apache Fineract > Issue Type: Sub-task >Affects Versions: 1.4.0 >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > Also include JpaSystemException as JPA exceptions with > DataIntegrityViolationException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1098) Add JpaSystemException as a JPA transaction exception
Yemdjih Kaze Nasser created FINERACT-1098: - Summary: Add JpaSystemException as a JPA transaction exception Key: FINERACT-1098 URL: https://issues.apache.org/jira/browse/FINERACT-1098 Project: Apache Fineract Issue Type: Sub-task Affects Versions: 1.4.0 Reporter: Yemdjih Kaze Nasser Also include JpaSystemException as JPA exceptions with DataIntegrityViolationException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1097) SchedularJob IT tests failing(org.awaitility.core.ConditionTimeoutException)
[
https://issues.apache.org/jira/browse/FINERACT-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165418#comment-17165418
]
Yemdjih Kaze Nasser commented on FINERACT-1097:
---
You are right about that. So this error is only likely to occur locally in
development as we do cause on travis each IT test I think run on a fresh
database so we will never have the error popup there.
Concerning an appropriate solution, maybe we could use some data from
fineract.dev([~vorburger] what do you think?) though I'm not sure if the data
from there is even close to being realistic enough. If IT tests are not enough
I can't really think of a way of simulating real world conditions for this.
> SchedularJob IT tests failing(org.awaitility.core.ConditionTimeoutException)
>
>
> Key: FINERACT-1097
> URL: https://issues.apache.org/jira/browse/FINERACT-1097
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Priority: Major
>
> While looking into
> [FINERACT-1069|https://issues.apache.org/jira/browse/FINERACT-1069], I
> stumbled upon some schedular IT test errors which I faced when working on
> migrating the JPA so originally I thought something was wrong with some of
> the changes I made. Seeing thesame error with OpenJPA on branch develop tells
> me this deserves more attention. Here are the logs:
>
> {code:java}
> SchedulerJobsTest > testTriggeringManualExecutionOfAllSchedulerJobs() FAILED
> org.awaitility.core.ConditionTimeoutException: Lambda expression in
> org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
> predicate to ret
> urn but it returned for input of <{version=4,
> jobRunStartTime=2020-07-26T16:52:28Z, jobRunEndTime=2020-07-26T16:52:47Z,
> status=success, triggerType=ap
> plication}> within 30 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:601)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:618)
> at
> org.apache.fineract.integrationtests.common.SchedulerJobHelper.executeAndAwaitJob(SchedulerJobHelper.java:165)
> at
> org.apache.fineract.integrationtests.SchedulerJobsTest.testTriggeringManualExecutionOfAllSchedulerJobs(SchedulerJobsTest.java:132)
> Caused by:
> java.util.concurrent.TimeoutException
> at
> java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> ... 6 more
> SchedulerJobsTestResults > testUpdateAccountingRunningBalancesJobOutcome()
> FAILED
> org.awaitility.core.ConditionTimeoutException: Lambda expression in
> org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
> predicate to ret
> urn but it returned for input of <{version=1,
> jobRunStartTime=2020-07-16T18:31:00Z, jobRunEndTime=2020-07-16T18:31:00Z,
> status=success, triggerType=cr
> on}> within 30 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:601)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:618)
> at
> org.apache.fineract.integrationtests.common.SchedulerJobHelper.executeAndAwaitJob(SchedulerJobHelper.java:165)
> at
> org.apache.fineract.integrationtests.SchedulerJobsTestResults.testUpdateAccountingRunningBalancesJobOutcome(SchedulerJobsTestResults.java:423)
> SchedulerJobsTestResults > testInterestPostingForSavingsJobOutcome() FAILED
> org.awaitility.core.ConditionTimeoutException: Lambda expression in
> org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
> predicate to ret
> urn but it returned for input of <{version=5,
> jobRunStartTime=2020-07-26T18:11:18Z, jobRunEndTime=2020-07-26T18:12:54Z,
> status=success, triggerType=ap
> plication}> within 30 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
>
[jira] [Created] (FINERACT-1097) SchedularJob IT tests failing(org.awaitility.core.ConditionTimeoutException)
Yemdjih Kaze Nasser created FINERACT-1097:
-
Summary: SchedularJob IT tests
failing(org.awaitility.core.ConditionTimeoutException)
Key: FINERACT-1097
URL: https://issues.apache.org/jira/browse/FINERACT-1097
Project: Apache Fineract
Issue Type: Improvement
Affects Versions: 1.4.0
Reporter: Yemdjih Kaze Nasser
While looking into
[FINERACT-1069|https://issues.apache.org/jira/browse/FINERACT-1069], I stumbled
upon some schedular IT test errors which I faced when working on migrating the
JPA so originally I thought something was wrong with some of the changes I
made. Seeing thesame error with OpenJPA on branch develop tells me this
deserves more attention. Here are the logs:
{code:java}
SchedulerJobsTest > testTriggeringManualExecutionOfAllSchedulerJobs() FAILED
org.awaitility.core.ConditionTimeoutException: Lambda expression in
org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
predicate to ret
urn but it returned for input of <{version=4,
jobRunStartTime=2020-07-26T16:52:28Z, jobRunEndTime=2020-07-26T16:52:47Z,
status=success, triggerType=ap
plication}> within 30 seconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
at
org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:601)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:618)
at
org.apache.fineract.integrationtests.common.SchedulerJobHelper.executeAndAwaitJob(SchedulerJobHelper.java:165)
at
org.apache.fineract.integrationtests.SchedulerJobsTest.testTriggeringManualExecutionOfAllSchedulerJobs(SchedulerJobsTest.java:132)
Caused by:
java.util.concurrent.TimeoutException
at
java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
at
org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
at
org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
... 6 more
SchedulerJobsTestResults > testUpdateAccountingRunningBalancesJobOutcome()
FAILED
org.awaitility.core.ConditionTimeoutException: Lambda expression in
org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
predicate to ret
urn but it returned for input of <{version=1,
jobRunStartTime=2020-07-16T18:31:00Z, jobRunEndTime=2020-07-16T18:31:00Z,
status=success, triggerType=cr
on}> within 30 seconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
at
org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:601)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:618)
at
org.apache.fineract.integrationtests.common.SchedulerJobHelper.executeAndAwaitJob(SchedulerJobHelper.java:165)
at
org.apache.fineract.integrationtests.SchedulerJobsTestResults.testUpdateAccountingRunningBalancesJobOutcome(SchedulerJobsTestResults.java:423)
SchedulerJobsTestResults > testInterestPostingForSavingsJobOutcome() FAILED
org.awaitility.core.ConditionTimeoutException: Lambda expression in
org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
predicate to ret
urn but it returned for input of <{version=5,
jobRunStartTime=2020-07-26T18:11:18Z, jobRunEndTime=2020-07-26T18:12:54Z,
status=success, triggerType=ap
plication}> within 30 seconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
at
org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:601)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:618)
at
org.apache.fineract.integrationtests.common.SchedulerJobHelper.executeAndAwaitJob(SchedulerJobHelper.java:165)
at
org.apache.fineract.integrationtests.SchedulerJobsTestResults.testInterestPostingForSavingsJobOutcome(SchedulerJobsTestResults.java:194)
SchedulerJobsTestResults > testInterestTransferForSavings() FAILED
org.awaitility.core.ConditionTimeoutException: Lambda expression in
org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
predicate to ret
urn but it returned for input of <{version=2,
[jira] [Updated] (FINERACT-1097) SchedularJob IT tests failing(org.awaitility.core.ConditionTimeoutException)
[
https://issues.apache.org/jira/browse/FINERACT-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser updated FINERACT-1097:
--
Issue Type: Bug (was: Improvement)
> SchedularJob IT tests failing(org.awaitility.core.ConditionTimeoutException)
>
>
> Key: FINERACT-1097
> URL: https://issues.apache.org/jira/browse/FINERACT-1097
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Priority: Major
>
> While looking into
> [FINERACT-1069|https://issues.apache.org/jira/browse/FINERACT-1069], I
> stumbled upon some schedular IT test errors which I faced when working on
> migrating the JPA so originally I thought something was wrong with some of
> the changes I made. Seeing thesame error with OpenJPA on branch develop tells
> me this deserves more attention. Here are the logs:
>
> {code:java}
> SchedulerJobsTest > testTriggeringManualExecutionOfAllSchedulerJobs() FAILED
> org.awaitility.core.ConditionTimeoutException: Lambda expression in
> org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
> predicate to ret
> urn but it returned for input of <{version=4,
> jobRunStartTime=2020-07-26T16:52:28Z, jobRunEndTime=2020-07-26T16:52:47Z,
> status=success, triggerType=ap
> plication}> within 30 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:601)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:618)
> at
> org.apache.fineract.integrationtests.common.SchedulerJobHelper.executeAndAwaitJob(SchedulerJobHelper.java:165)
> at
> org.apache.fineract.integrationtests.SchedulerJobsTest.testTriggeringManualExecutionOfAllSchedulerJobs(SchedulerJobsTest.java:132)
> Caused by:
> java.util.concurrent.TimeoutException
> at
> java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> ... 6 more
> SchedulerJobsTestResults > testUpdateAccountingRunningBalancesJobOutcome()
> FAILED
> org.awaitility.core.ConditionTimeoutException: Lambda expression in
> org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
> predicate to ret
> urn but it returned for input of <{version=1,
> jobRunStartTime=2020-07-16T18:31:00Z, jobRunEndTime=2020-07-16T18:31:00Z,
> status=success, triggerType=cr
> on}> within 30 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:601)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:618)
> at
> org.apache.fineract.integrationtests.common.SchedulerJobHelper.executeAndAwaitJob(SchedulerJobHelper.java:165)
> at
> org.apache.fineract.integrationtests.SchedulerJobsTestResults.testUpdateAccountingRunningBalancesJobOutcome(SchedulerJobsTestResults.java:423)
> SchedulerJobsTestResults > testInterestPostingForSavingsJobOutcome() FAILED
> org.awaitility.core.ConditionTimeoutException: Lambda expression in
> org.apache.fineract.integrationtests.common.SchedulerJobHelper: expected the
> predicate to ret
> urn but it returned for input of <{version=5,
> jobRunStartTime=2020-07-26T18:11:18Z, jobRunEndTime=2020-07-26T18:12:54Z,
> status=success, triggerType=ap
> plication}> within 30 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:601)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:618)
> at
> org.apache.fineract.integrationtests.common.SchedulerJobHelper.executeAndAwaitJob(SchedulerJobHelper.java:165)
> at
>
[jira] [Assigned] (FINERACT-1069) RecurringDepositTest / FixedDepositTests failing on 1st of month
[ https://issues.apache.org/jira/browse/FINERACT-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1069: - Assignee: Yemdjih Kaze Nasser > RecurringDepositTest / FixedDepositTests failing on 1st of month > > > Key: FINERACT-1069 > URL: https://issues.apache.org/jira/browse/FINERACT-1069 > Project: Apache Fineract > Issue Type: Bug >Reporter: Petri Tuomola >Assignee: Yemdjih Kaze Nasser >Priority: Major > > It seems that the calculation to determine expected interest in > RecurringDepositTest / FixedDepositTest breaks on 1st day of (each or some?) > months: seems that the logic calculates one day too much interest, and hence > the tests fail. This can be reproduced by setting system time to e.g. 1st > July and running the tests. This should be fixed as otherwise the builds will > always fail on this once a month. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1069) RecurringDepositTest / FixedDepositTests failing on 1st of month
[ https://issues.apache.org/jira/browse/FINERACT-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165256#comment-17165256 ] Yemdjih Kaze Nasser commented on FINERACT-1069: --- I will take on this. I've seen this error a couple of times while working on migrating the ORM. > RecurringDepositTest / FixedDepositTests failing on 1st of month > > > Key: FINERACT-1069 > URL: https://issues.apache.org/jira/browse/FINERACT-1069 > Project: Apache Fineract > Issue Type: Bug >Reporter: Petri Tuomola >Priority: Major > > It seems that the calculation to determine expected interest in > RecurringDepositTest / FixedDepositTest breaks on 1st day of (each or some?) > months: seems that the logic calculates one day too much interest, and hence > the tests fail. This can be reproduced by setting system time to e.g. 1st > July and running the tests. This should be fixed as otherwise the builds will > always fail on this once a month. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1091) PersistenceException: Field 'constitution_cv_id' doesn't have a default value
[
https://issues.apache.org/jira/browse/FINERACT-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159522#comment-17159522
]
Yemdjih Kaze Nasser commented on FINERACT-1091:
---
No this is not one of the issues. This is probably something else. I'd bet on
what [~ptuomola] proposes.
> PersistenceException: Field 'constitution_cv_id' doesn't have a default value
> -
>
> Key: FINERACT-1091
> URL: https://issues.apache.org/jira/browse/FINERACT-1091
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Michael Vorburger
>Priority: Blocker
>
> See FINERACT-932 for general background; I've found this in logs of
> [https://www.fineract.dev|https://www.fineract.dev/]:
> {noformat}org.apache.openjpa.persistence.PersistenceException: The
> transaction has been rolled back. See the nested exceptions for details on
> the errors that occurred.
> at
> org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2470)
> ~[openjpa-3.1.1.jar:3.1.1]
> at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2308)
> ~[openjpa-3.1.1.jar:3.1.1]
> at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:2199)
> ~[openjpa-3.1.1.jar:3.1.1]
> at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1962)
> ~[openjpa-3.1.1.jar:3.1.1]
> at
> org.apache.openjpa.kernel.StateManagerImpl.assignObjectId(StateManagerImpl.java:618)
> ~[openjpa-3.1.1.jar:3.1.1]
> at
> org.apache.openjpa.kernel.StateManagerImpl.assignField(StateManagerImpl.java:705)
> ~[openjpa-3.1.1.jar:3.1.1]
> at
> org.apache.openjpa.kernel.StateManagerImpl.beforeAccessField(StateManagerImpl.java:1750)
> ~[openjpa-3.1.1.jar:3.1.1]
> at
> org.apache.openjpa.kernel.StateManagerImpl.accessingField(StateManagerImpl.java:1679)
> ~[openjpa-3.1.1.jar:3.1.1]
> at
> org.apache.fineract.infrastructure.core.domain.AbstractPersistableCustom.pcGetid(AbstractPersistableCustom.java)
> ~[app/:na]
> at
> org.apache.fineract.infrastructure.core.domain.AbstractPersistableCustom.getId(AbstractPersistableCustom.java:50)
> ~[app/:na]
> at
> org.apache.fineract.portfolio.address.service.AddressWritePlatformServiceImpl.addNewClientAddress(AddressWritePlatformServiceImpl.java:143)
> ~[app/:na]
> at
> org.apache.fineract.portfolio.client.service.ClientWritePlatformServiceJpaRepositoryImpl.createClient(ClientWritePlatformServiceJpaRepositoryImpl.java:328)
> ~[app/:na]
> at
> org.apache.fineract.portfolio.client.service.ClientWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$71ca1b7f.invoke()
> ~[app/:na]
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> ~[spring-core-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
> ~[spring-aop-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> ~[spring-aop-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
> ~[spring-aop-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:366)
> ~[spring-tx-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:118)
> ~[spring-tx-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> ~[spring-aop-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
> ~[spring-aop-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691)
> ~[spring-aop-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
> org.apache.fineract.portfolio.client.service.ClientWritePlatformServiceJpaRepositoryImpl$$EnhancerBySpringCGLIB$$3e889443.createClient()
> ~[app/:na]
> at
> org.apache.fineract.portfolio.client.handler.CreateClientCommandHandler.processCommand(CreateClientCommandHandler.java:45)
> ~[app/:na]
> at
> org.apache.fineract.portfolio.client.handler.CreateClientCommandHandler$$FastClassBySpringCGLIB$$6bce1ca9.invoke()
> ~[app/:na]
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> ~[spring-core-5.2.6.RELEASE.jar:5.2.6.RELEASE]
> at
>
[jira] [Assigned] (FINERACT-1079) Run Task spotlessApply before compileJava?
[ https://issues.apache.org/jira/browse/FINERACT-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1079: - Assignee: Awasum Yannick > Run Task spotlessApply before compileJava? > -- > > Key: FINERACT-1079 > URL: https://issues.apache.org/jira/browse/FINERACT-1079 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Awasum Yannick >Assignee: Awasum Yannick >Priority: Minor > Fix For: 1.4.0 > > > Developers consistently have problems manually running the spotlessApply task > after coding changes... See: [https://github.com/apache/fineract/pull/1151] > and [https://github.com/apache/fineract/pull/1148] > maybe we should just run spotlessApply just before compilation and skip the > tasks to check for spotless failures? Or we run both of them: Run > spotlessApply before spotlessCheck (seems wasteful). Is this a good idea? I > wonder? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1079) Run Task spotlessApply before compileJava?
[ https://issues.apache.org/jira/browse/FINERACT-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-1079. --- Resolution: Fixed > Run Task spotlessApply before compileJava? > -- > > Key: FINERACT-1079 > URL: https://issues.apache.org/jira/browse/FINERACT-1079 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Awasum Yannick >Assignee: Awasum Yannick >Priority: Minor > Fix For: 1.4.0 > > > Developers consistently have problems manually running the spotlessApply task > after coding changes... See: [https://github.com/apache/fineract/pull/1151] > and [https://github.com/apache/fineract/pull/1148] > maybe we should just run spotlessApply just before compilation and skip the > tasks to check for spotless failures? Or we run both of them: Run > spotlessApply before spotlessCheck (seems wasteful). Is this a good idea? I > wonder? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1077) Migrate from legacy plugins applications to plugins DSL in build.gradle
[ https://issues.apache.org/jira/browse/FINERACT-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser reassigned FINERACT-1077: - Assignee: Yemdjih Kaze Nasser > Migrate from legacy plugins applications to plugins DSL in build.gradle > --- > > Key: FINERACT-1077 > URL: https://issues.apache.org/jira/browse/FINERACT-1077 > Project: Apache Fineract > Issue Type: Improvement > Components: Build >Affects Versions: 1.4.0 >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Major > > We are still using the old way of applying gradle plugins in our > build.gradle. Today there is more convenient way of doing this which more and > more packages are using. This would make the build less cumbersome too and > plugins easier to maintain and apply. > [https://docs.gradle.org/current/userguide/plugins.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1078) Make spring logs colorful
Yemdjih Kaze Nasser created FINERACT-1078: - Summary: Make spring logs colorful Key: FINERACT-1078 URL: https://issues.apache.org/jira/browse/FINERACT-1078 Project: Apache Fineract Issue Type: Improvement Components: Build Affects Versions: 1.4.0 Reporter: Yemdjih Kaze Nasser [~vorburger] once expressed this in a comment. Adding springs support for colored build logs which could be useful, making logs more readable and errors easier to spot. I just think it's a great feature to add. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1023) Update dependency spring-boot-gradle-plugin from v2.2.7 to v2.3.1.RELEASE
[ https://issues.apache.org/jira/browse/FINERACT-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser resolved FINERACT-1023. --- Resolution: Fixed > Update dependency spring-boot-gradle-plugin from v2.2.7 to v2.3.1.RELEASE > - > > Key: FINERACT-1023 > URL: https://issues.apache.org/jira/browse/FINERACT-1023 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Awasum Yannick >Assignee: Percy Ashu >Priority: Minor > Fix For: 1.4.0 > > > Renovate tried to upgrade to Spring Boot 2.3: > [https://github.com/apache/fineract/pull/998] > This failed as shown here: > [https://travis-ci.org/github/apache/fineract/builds/695663148] > Looks like validation dependency is missing in the new release. We have to > upgrade manually by adding it? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1023) Update dependency spring-boot-gradle-plugin from v2.2.7 to v2.3.1.RELEASE
[ https://issues.apache.org/jira/browse/FINERACT-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINERACT-1023: -- Affects Version/s: 1.4.0 > Update dependency spring-boot-gradle-plugin from v2.2.7 to v2.3.1.RELEASE > - > > Key: FINERACT-1023 > URL: https://issues.apache.org/jira/browse/FINERACT-1023 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Awasum Yannick >Assignee: Percy Ashu >Priority: Minor > Fix For: 1.4.0 > > > Renovate tried to upgrade to Spring Boot 2.3: > [https://github.com/apache/fineract/pull/998] > This failed as shown here: > [https://travis-ci.org/github/apache/fineract/builds/695663148] > Looks like validation dependency is missing in the new release. We have to > upgrade manually by adding it? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1077) Migrate from legacy plugins applications to plugins DSL in build.gradle
[ https://issues.apache.org/jira/browse/FINERACT-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINERACT-1077: -- Affects Version/s: (was: 1.5.0) 1.4.0 > Migrate from legacy plugins applications to plugins DSL in build.gradle > --- > > Key: FINERACT-1077 > URL: https://issues.apache.org/jira/browse/FINERACT-1077 > Project: Apache Fineract > Issue Type: Improvement > Components: Build >Affects Versions: 1.4.0 >Reporter: Yemdjih Kaze Nasser >Priority: Major > > We are still using the old way of applying gradle plugins in our > build.gradle. Today there is more convenient way of doing this which more and > more packages are using. This would make the build less cumbersome too and > plugins easier to maintain and apply. > [https://docs.gradle.org/current/userguide/plugins.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1077) Migrate from legacy plugins applications to plugins DSL in build.gradle
Yemdjih Kaze Nasser created FINERACT-1077: - Summary: Migrate from legacy plugins applications to plugins DSL in build.gradle Key: FINERACT-1077 URL: https://issues.apache.org/jira/browse/FINERACT-1077 Project: Apache Fineract Issue Type: Improvement Components: Build Affects Versions: 1.5.0 Reporter: Yemdjih Kaze Nasser We are still using the old way of applying gradle plugins in our build.gradle. Today there is more convenient way of doing this which more and more packages are using. This would make the build less cumbersome too and plugins easier to maintain and apply. [https://docs.gradle.org/current/userguide/plugins.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1022) Update ehcache: 2.10.6 to current 3.8.1
[ https://issues.apache.org/jira/browse/FINERACT-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146530#comment-17146530 ] Yemdjih Kaze Nasser commented on FINERACT-1022: --- Thanks [~ptuomola] for going ahead and dealing with this. That's really awesome. > Update ehcache: 2.10.6 to current 3.8.1 > --- > > Key: FINERACT-1022 > URL: https://issues.apache.org/jira/browse/FINERACT-1022 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Yemdjih Kaze Nasser >Assignee: Yemdjih Kaze Nasser >Priority: Blocker > Fix For: 1.4.0 > > > Update artifactory and version number -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1050) loan_repayment_schedule_id column contraint errors
[
https://issues.apache.org/jira/browse/FINERACT-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser updated FINERACT-1050:
--
Summary: loan_repayment_schedule_id column contraint errors (was: Failing
ClientLoanIntegrationTest)
> loan_repayment_schedule_id column contraint errors
> --
>
> Key: FINERACT-1050
> URL: https://issues.apache.org/jira/browse/FINERACT-1050
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Priority: Major
>
> Dupicate value for column loan_repayment_schedule_id. I think the entity
> relationship around this column are messed up. I don't know how they manage
> to work till now but eclipselink doesn't seem to agree with it.
> {code:java}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
> java.sql.SQLIntegrityConstraintViolationException: Column
> 'loan_repayment_schedule_id' cannot be null\nError Code: 1048\nCall: INSERT
> INTO m_loan_transaction_repayment_schedule_mapping (loan_transaction_id, ID,
> amount, fee_charges_portion_derived, interest_portion_derived,
> penalty_charges_portion_derived, principal_portion_derived,
> loan_repayment_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [5022,
> null, 412.00, null, 12.00, null, 400.00, null]\nQuery:
> ValueReadQuery(name=\"SEQ_GEN_IDENTITY\" sql=\"SELECT LAST_INSERT_ID()\");
> nested exception is javax.persistence.PersistenceException: Exception
> [EclipseLink-4002] (Eclipse Persistence Services -
> 2.7.7.v20200504-69f2c2b80d):
> org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
> java.sql.SQLIntegrityConstraintViolationException: Column
> 'loan_repayment_schedule_id' cannot be null\nError Code: 1048\nCall: INSERT
> INTO m_loan_transaction_repayment_schedule_mapping (loan_transaction_id, ID,
> amount, fee_charges_portion_derived, interest_portion_derived,
> penalty_charges_portion_derived, principal_portion_derived,
> loan_repayment_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [5022,
> null, 412.00, null, 12.00, null, 400.00, null]\nQuery:
> ValueReadQuery(name=\"SEQ_GEN_IDENTITY\" sql=\"SELECT
> LAST_INSERT_ID()\")","path":"/fineract-provider/api/v1/loans/1113"}"
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FINERACT-1050) Failing ClientLoanIntegrationTest
[
https://issues.apache.org/jira/browse/FINERACT-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser updated FINERACT-1050:
--
Description:
Dupicate value for column loan_repayment_schedule_id. I think the entity
relationship around this column are messed up. I don't know how they manage to
work till now but eclipselink doesn't seem to agree with it.
{code:java}
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.7.7.v20200504-69f2c2b80d):
org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
java.sql.SQLIntegrityConstraintViolationException: Column
'loan_repayment_schedule_id' cannot be null\nError Code: 1048\nCall: INSERT
INTO m_loan_transaction_repayment_schedule_mapping (loan_transaction_id, ID,
amount, fee_charges_portion_derived, interest_portion_derived,
penalty_charges_portion_derived, principal_portion_derived,
loan_repayment_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [5022,
null, 412.00, null, 12.00, null, 400.00, null]\nQuery:
ValueReadQuery(name=\"SEQ_GEN_IDENTITY\" sql=\"SELECT LAST_INSERT_ID()\");
nested exception is javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.7.7.v20200504-69f2c2b80d):
org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
java.sql.SQLIntegrityConstraintViolationException: Column
'loan_repayment_schedule_id' cannot be null\nError Code: 1048\nCall: INSERT
INTO m_loan_transaction_repayment_schedule_mapping (loan_transaction_id, ID,
amount, fee_charges_portion_derived, interest_portion_derived,
penalty_charges_portion_derived, principal_portion_derived,
loan_repayment_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [5022,
null, 412.00, null, 12.00, null, 400.00, null]\nQuery:
ValueReadQuery(name=\"SEQ_GEN_IDENTITY\" sql=\"SELECT
LAST_INSERT_ID()\")","path":"/fineract-provider/api/v1/loans/1113"}"
{code}
was:
Dupicate value for column loan_repayment_schedule_id. I think the entity
relationship around this column are messed up. I don't know how they manage to
work till now but eclipselink doesn't seem to agree with it.
{code:java}
java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <500>.
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at
org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:72)
at
org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:59)
at
org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:277)
at
io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:493)
at
io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown
Source)
at
io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1656)
at jdk.internal.reflect.GeneratedMethodAccessor85.invoke(Unknown Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:107)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:323)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1262)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1029)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:816)
at groovy.lang.GroovyObject.invokeMethod(GroovyObject.java:39)
at
org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:45)
at
org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:55)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:203)
at
io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1661)
at jdk.internal.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
[jira] [Updated] (FINERACT-1050) Failing ClientLoanIntegrationTest
[
https://issues.apache.org/jira/browse/FINERACT-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser updated FINERACT-1050:
--
Description:
Dupicate value for column loan_repayment_schedule_id. I think the entity
relationship around this column are messed up. I don't know how they manage to
work till now but eclipselink doesn't seem to agree with it.
{code:java}
java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <500>.
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at
org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:72)
at
org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:59)
at
org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:277)
at
io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:493)
at
io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown
Source)
at
io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1656)
at jdk.internal.reflect.GeneratedMethodAccessor85.invoke(Unknown Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:107)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:323)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1262)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1029)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:816)
at groovy.lang.GroovyObject.invokeMethod(GroovyObject.java:39)
at
org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:45)
at
org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:55)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:203)
at
io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1661)
at jdk.internal.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:107)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:323)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1262)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1029)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:816)
at groovy.lang.GroovyObject.invokeMethod(GroovyObject.java:39)
at
org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:45)
at
org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:55)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:203)
at
io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
at
io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
at
org.apache.fineract.integrationtests.common.Utils.performServerPost(Utils.java:154)
at
org.apache.fineract.integrationtests.common.loans.LoanTransactionHelper.performLoanTransaction(LoanTransactionHelper.java:590)
at
org.apache.fineract.integrationtests.common.loans.LoanTransactionHelper.forecloseLoan(LoanTransactionHelper.java:296)
at
org.apache.fineract.integrationtests.ClientLoanIntegrationTest.testLoanForeclosure(ClientLoanIntegrationTest.java:4999)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
[jira] [Updated] (FINERACT-1051) Failing RecurringDepositTest
[
https://issues.apache.org/jira/browse/FINERACT-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser updated FINERACT-1051:
--
Affects Version/s: 1.4.0
> Failing RecurringDepositTest
> -
>
> Key: FINERACT-1051
> URL: https://issues.apache.org/jira/browse/FINERACT-1051
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Yemdjih Kaze Nasser
>Priority: Major
>
> {code:java}
> org.opentest4j.AssertionFailedError: Verifying Pre-Closure maturity amount
> ==> expected: <4014.0> but was: <4002.0>
> at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
> at
> org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:787)
> at
> org.apache.fineract.integrationtests.RecurringDepositTest.testPrematureClosureAmountWithPenalInterestForWholeTerm_With_360_Days(RecurringDepositTest.java:1859)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:675)
> at
> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:125)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:132)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:124)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:74)
> at
> org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
> at
> org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:104)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:62)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:43)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:35)
> at
> org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
> at
> org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$6(TestMethodTestDescriptor.java:202)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:198)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:135)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:69)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:135)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:125)
> at
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:135)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:123)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:122)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:80)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1540)
> at
>
[jira] [Updated] (FINERACT-1048) SchedulerJob executeAndAwait predicate returns false with successful transaction
[ https://issues.apache.org/jira/browse/FINERACT-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yemdjih Kaze Nasser updated FINERACT-1048: -- Affects Version/s: 1.4.0 > SchedulerJob executeAndAwait predicate returns false with successful > transaction > > > Key: FINERACT-1048 > URL: https://issues.apache.org/jira/browse/FINERACT-1048 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Yemdjih Kaze Nasser >Priority: Major > > Schedularjob acting crazy again. Time execution time comparison is faulty in > tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1051) Failing RecurringDepositTest
Yemdjih Kaze Nasser created FINERACT-1051:
-
Summary: Failing RecurringDepositTest
Key: FINERACT-1051
URL: https://issues.apache.org/jira/browse/FINERACT-1051
Project: Apache Fineract
Issue Type: Bug
Reporter: Yemdjih Kaze Nasser
{code:java}
org.opentest4j.AssertionFailedError: Verifying Pre-Closure maturity amount ==>
expected: <4014.0> but was: <4002.0>
at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
at
org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:787)
at
org.apache.fineract.integrationtests.RecurringDepositTest.testPrematureClosureAmountWithPenalInterestForWholeTerm_With_360_Days(RecurringDepositTest.java:1859)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:675)
at
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:125)
at
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:132)
at
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:124)
at
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:74)
at
org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
at
org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:104)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:62)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:43)
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:35)
at
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
at
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$6(TestMethodTestDescriptor.java:202)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:198)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:135)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:69)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:135)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:125)
at
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:135)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:123)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:122)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:80)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1540)
at
org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:38)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:139)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at
