As promised, I'll be sending out a weekly list of "Fineract Issues Resolved
Last Week" (and, separately, current open Blocker issues).

For the past week, the project wishes to acknowledge the contributions made
by, and very much thanks:

* Awasum
* Manoj
* Natasha
* Percy
* Petri

Full list with details here:



Issue Subscription
Filter: Fineract Resolved Last Week
<https://issues.apache.org/jira/issues/?filter=12349018> (9 issues)


Subscriber: vorburger
T Patch Info Key Summary Assignee Reporter P Status Resolution Created Updated
Due Development
<https://issues.apache.org/jira/browse/FINERACT-1011>
[image: image.png]



<https://issues.apache.org/jira/browse/FINERACT-1011>
FINERACT-1011 <https://issues.apache.org/jira/browse/FINERACT-1011>

Execution failed for task ':cargoStartLocal' when running IntegrationTest
locally <https://issues.apache.org/jira/browse/FINERACT-1011>
Awasum Yannick
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=awasum> Awasum
Yannick <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=awasum>
[image: image.png]



Resolved Fixed 27/May/20 29/May/20
<https://issues.apache.org/jira/browse/FINERACT-1008>
[image: image.png]



<https://issues.apache.org/jira/browse/FINERACT-1008>
FINERACT-1008 <https://issues.apache.org/jira/browse/FINERACT-1008>

Field 'version_rank' doesn't have a default value (blocking updates on
fineract.dev) <https://issues.apache.org/jira/browse/FINERACT-1008>
Manoj <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fynmanoj>
Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger>
[image: image.png]



Resolved Fixed 26/May/20 31/May/20
<https://issues.apache.org/jira/browse/FINERACT-893>
[image: image.png]



<https://issues.apache.org/jira/browse/FINERACT-893>
FINERACT-893 <https://issues.apache.org/jira/browse/FINERACT-893>

Fixed Deposit - Maturity instructions for rollover
<https://issues.apache.org/jira/browse/FINERACT-893>
Manoj <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fynmanoj>
Manoj <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fynmanoj>
[image: image.png]



Closed Fixed 14/Apr/20 27/May/20
<https://issues.apache.org/jira/browse/FINERACT-966>
[image: image.png]



<https://issues.apache.org/jira/browse/FINERACT-966>
FINERACT-966 <https://issues.apache.org/jira/browse/FINERACT-966>

Bump dom4j from 2.1.0 to 2.1.3
<https://issues.apache.org/jira/browse/FINERACT-966>
Natasha Natarajan
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=natashan> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger>
[image: image.png]



Resolved Fixed 10/May/20 29/May/20
<https://issues.apache.org/jira/browse/FINERACT-804>
[image: image.png]



<https://issues.apache.org/jira/browse/FINERACT-804>
FINERACT-804 <https://issues.apache.org/jira/browse/FINERACT-804>

Use OkHTTP v3 or at least 2.7.5 instead of 2.0.0
<https://issues.apache.org/jira/browse/FINERACT-804>
Natasha Natarajan
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=natashan> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger>
[image: image.png]



Resolved Fixed 02/Dec/19 27/May/20
<https://issues.apache.org/jira/browse/FINERACT-1014>
[image: image.png]



<https://issues.apache.org/jira/browse/FINERACT-1014>
FINERACT-1014 <https://issues.apache.org/jira/browse/FINERACT-1014>

From/To Amount Range and Period Validatation broken
<https://issues.apache.org/jira/browse/FINERACT-1014>
Percy Ashu
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Percy%20Ashu>
Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger>
[image: image]

Resolved Fixed 01/Jun/20 01/Jun/20
<https://issues.apache.org/jira/browse/FINERACT-918>
[image: image.png]



<https://issues.apache.org/jira/browse/FINERACT-918>
FINERACT-918 <https://issues.apache.org/jira/browse/FINERACT-918>

Document how to run Fineract in IDEs like Eclipse & IntelliJ - great for
easy debugging! <https://issues.apache.org/jira/browse/FINERACT-918>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> Michael
Vorburger
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vorburger>
[image: image.png]



Resolved Fixed 03/May/20 01/Jun/20
<https://issues.apache.org/jira/browse/FINERACT-1005>
[image: image.png]



<https://issues.apache.org/jira/browse/FINERACT-1005>
FINERACT-1005 <https://issues.apache.org/jira/browse/FINERACT-1005>

Fix Failing test in org.apache.fineract.integrationtests.StaffTest
<https://issues.apache.org/jira/browse/FINERACT-1005>
Petri Tuomola
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ptuomola> Percy
Ashu
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Percy%20Ashu>
[image: image]

Resolved Fixed 25/May/20 01/Jun/20
<https://issues.apache.org/jira/browse/FINERACT-1003>
[image: image]

<https://issues.apache.org/jira/browse/FINERACT-1003>
FINERACT-1003 <https://issues.apache.org/jira/browse/FINERACT-1003>

FINERACT-849 <https://issues.apache.org/jira/browse/FINERACT-849> Default
no-args constructors for jpa
<https://issues.apache.org/jira/browse/FINERACT-1003>
Yemdjih Kaze Nasser
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kaze> Yemdjih
Kaze Nasser
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kaze>
[image: image.png]



Resolved Fixed 24/May/20 01/Jun/20
You may edit this subscription here
<https://issues.apache.org/jira/secure/EditSubscription!default.jspa?subId=23124&filterId=12349018>.


This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)

[image: image.png]
Title: Unusual Usage - Account Temporarily Locked Down
Gmail by Google
 
Unusual Usage - Account Temporarily Locked Down


To keep our systems healthy, Google has temporarily disabled your account. This primarily occurs when we detect unusually high levels of activity on your account. In most cases, it should take one hour to regain access. In rare cases, it can take up to 24 hours for access to be reinstated.

We’re sorry for the inconvenience.

Here are some reasons why this could have happened:

  1. Receiving, deleting, or downloading large amounts of mail via POP or IMAP in a short period of time.
  2. Sending a large number of messages to many people.
  3. Being logged into or synchronizing Gmail on many computers, clients, or mobile devices.
  4. Browser-related issues. If you find your browser continually reloading while attempting to access your Inbox, it’s probably a browser issue, and it may be necessary to clear your browser’s cache and cookies.
  5. Providing access to file-sharing, file-storage software, email analytics services, browser extensions, or third party software that automatically logs in to your Gmail account.

For more help troubleshooting this issue, click here. For G Suite or Google Apps users, please contact your administrator if you have any further issues.

 

 

 

 


©2020 Google - Gmail Home - Privacy Policy - Program Policies - Terms of Use - Google Home

 

Title: Unusual Usage - Account Temporarily Locked Down
Gmail by Google
 
Unusual Usage - Account Temporarily Locked Down


To keep our systems healthy, Google has temporarily disabled your account. This primarily occurs when we detect unusually high levels of activity on your account. In most cases, it should take one hour to regain access. In rare cases, it can take up to 24 hours for access to be reinstated.

We’re sorry for the inconvenience.

Here are some reasons why this could have happened:

  1. Receiving, deleting, or downloading large amounts of mail via POP or IMAP in a short period of time.
  2. Sending a large number of messages to many people.
  3. Being logged into or synchronizing Gmail on many computers, clients, or mobile devices.
  4. Browser-related issues. If you find your browser continually reloading while attempting to access your Inbox, it’s probably a browser issue, and it may be necessary to clear your browser’s cache and cookies.
  5. Providing access to file-sharing, file-storage software, email analytics services, browser extensions, or third party software that automatically logs in to your Gmail account.

For more help troubleshooting this issue, click here. For G Suite or Google Apps users, please contact your administrator if you have any further issues.

 

 

 

 


©2020 Google - Gmail Home - Privacy Policy - Program Policies - Terms of Use - Google Home

 

Title: Unusual Usage - Account Temporarily Locked Down
Gmail by Google
 
Unusual Usage - Account Temporarily Locked Down


To keep our systems healthy, Google has temporarily disabled your account. This primarily occurs when we detect unusually high levels of activity on your account. In most cases, it should take one hour to regain access. In rare cases, it can take up to 24 hours for access to be reinstated.

We’re sorry for the inconvenience.

Here are some reasons why this could have happened:

  1. Receiving, deleting, or downloading large amounts of mail via POP or IMAP in a short period of time.
  2. Sending a large number of messages to many people.
  3. Being logged into or synchronizing Gmail on many computers, clients, or mobile devices.
  4. Browser-related issues. If you find your browser continually reloading while attempting to access your Inbox, it’s probably a browser issue, and it may be necessary to clear your browser’s cache and cookies.
  5. Providing access to file-sharing, file-storage software, email analytics services, browser extensions, or third party software that automatically logs in to your Gmail account.

For more help troubleshooting this issue, click here. For G Suite or Google Apps users, please contact your administrator if you have any further issues.

 

 

 

 


©2020 Google - Gmail Home - Privacy Policy - Program Policies - Terms of Use - Google Home

 

Reply via email to