Re: Releasing Apache Fineract 1.1 WAS [Fwd: Intergration test]

[Avik Ganguly]

Hi guys,

Is Steve's changes getting reflected in the release notes

?

If the release notes is up to date, I can give the release this Thursday
after merging one pending item from my side.

Regards,
Avik.

On Sun, Feb 25, 2018 at 9:13 PM, Ed Cable  wrote:

> Fineract committers,
>
> Now that the PRs have been submitted for all the outstanding critical bug
> fixes and integration test failures, can we please review, merge, and get
> the release prepped and call for the vote!
>
> As you know the community has waiting on this for quite some time now and
> I"d like to get this shipped and shift focuses to Fineract 1.2
>
> Thanks!
>
> Ed
> -- Forwarded message --
> From: Ed Cable 
> Date: Sun, Feb 18, 2018 at 4:49 AM
> Subject: Re: Intergration test
> To: Dev 
> Cc: Vishwas Babu A J , Nazeer Hussain
> Shaik , Kumaranath Fernando <
> kumaranathferna...@gmail.com>, Avik Ganguly ,
> Nikhil Pawar , Santosh Math <
> sant...@confluxtechnologies.com>
>
>
> Great!
>
> Committers, can you please review?
>
> Nazeer, with this fix and Steve's for the notification, I think we're
> ready to move forward. Can you initiate the next steps in the release
> process?
>
> Thanks,
>
> Ed
>
> On Sat, Feb 17, 2018 at 11:20 AM, Kumaranath Fernando <
> kumaranathferna...@gmail.com> wrote:
>
>> Hi Ed!
>>
>> I've just sent a PR 
>> correcting the integration test failures.
>>
>> Regards,
>> Kumaranath Fernando
>>
>> On Fri, Feb 16, 2018 at 6:14 PM, Ed Cable  wrote:
>>
>>> Thanks for the feedback Vishwas. Kumaranath, hopefully you have enough
>>> to go by now and can make those changes. I believe Steve fixed our other
>>> outstanding issue so once we can get these integration tests to pass we'll
>>> be ready to call for a vote on the release.
>>>
>>> Ed
>>>
>>> On Wed, Feb 14, 2018 at 1:06 PM, 
>>> wrote:
>>>
 The approach of sleeping for a fixed time does not work well in general
 as Integration test cases must pass on any environment. Depending on random
 sleep values would mean that there is always a probability that the test
 can fail if the system is slow / has other CPU intensive processes running
 etc.

 Ideally , you would handle such scenarios more gracefully . Have the
 test check if the file you are referring to is created , if not sleep for
 an interval and check again etc.

 Please make this change and send out a pull request

 Regards,
 Vishwas

 On Feb 14, 2018, at 9:39 AM, Kumaranath Fernando <
 kumaranathferna...@gmail.com> wrote:

 I've tested the develop branch and it's most likely because the result
 excel file takes a bit of time to be created, after the file is created I'm
 trying to read a value of a column.
 Since the file is not created by the time FileInputStream reads the
 file, you get a FileNotException.

 You could fix this issue by increasing the number of milliseconds 1
 on Thread.sleep() line in the respective tests.Ping me if this resolves the
 issue and I'll send PR.

 Vishwas/Nazeer awaiting your confirmation!.

 Regards,
 Kumaranath Fernando


 On Wed, Feb 14, 2018 at 10:59 AM, vishwas <
 vish...@confluxtechnologies.com> wrote:

> Hi Kumaranath,
>
> You should be able to reproduce this issue if you fetch the latest
> fineract code in a seperate workspace.
>
> If the remember correctly, the crux of the issue seemed be be that
> files you were referring to in the test cases , i.e
> fineract-provider/src/integrationtest/resources/bulkimport/importhandler/officer
> are not present and all these tests cases throw a file not found 
> exception.
>
> Regards,
> Vishwas
>
>
>
> > On Feb 13, 2018, at 6:43 PM, Kumaranath Fernando <
> kumaranathferna...@gmail.com> wrote:
> >
> > Hi Nazeer!
> >
> > Could you please send in the stack traces for investigation.
> >
> > Regards,
> > Kumaranath Fernando
> >
> > On Wed, Feb 14, 2018 at 12:43 AM, Ed Cable  > wrote:
> >
> >> Please keep the community posted and try to address as quickly as
> you can
> >> we have one other issue we're fixing and then once these
> integration tests
> >> pass, we can call for a vote to ship the release.
> >>
> >> Ed
> >>
> >> On Tue, Feb 13, 2018 at 6:02 AM, Kumaranath Fernando <
> >> kumaranathferna...@gmail.com> wrote:
> >>
> >>> Hello Ed!
> >>>
> >>> Sure. I'll take a look at it!
> >>>
> >>> Regards,
> >>> Kumaranath Fernando
> >>>
> >>> On Tue, Feb 13, 2018 at 11:40 AM, Ed Cable 
> wrote:
> >>>
>  Kumaranath,
> 
>  Could you please look into these failing integration tests? It's
> one of
>  the 

Re: Relesea Dates/Scheduling - Mifos / Fineract

[Ed Cable]

Victor,

Good and timely question as we're trying to solidify our processes around
this based on recent discussion at https://goo.gl/qUBZqd

For the Fineract side of things, please see below.

In the near-term, please reference these wiki pages for an overview of some
of the timeline related to our time-driven release processes:
https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Releases and
here for the timing related to Fineract 1.2:
https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract

We'll soon have a scrum board configured to assist in planning for the
Fineract 1.2 and Fineract 1.3 releases.

Thanks,

Ed

On Mon, Feb 26, 2018 at 9:26 PM, Victor Romero <
victor.rom...@fintecheando.mx> wrote:

> Hi,
>
> Is there any place where I can review the release dates/scheduling of
> Mifos / Fineract?
>
>
> Or how are managed the releases ?
>
> I am looking something like this:
>
> Resultado de imagen para ubuntu releases
>
>


-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
<(484)%20477-8649>

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Re: Getting started on Fineract CN

[Isaac Kamga]

Hi Myrle,

+Awasum

Thanks for all the awesomeness !

@Myrle, While awaiting your review of the PR, I'll be on those tasks.

@Awasum, thanks for the dependency graph, it's definitely very helpful.

At Your Service,
Isaac Kamga.


On Tue, Feb 27, 2018 at 7:55 PM, Awasum Yannick  wrote:

> Hi Isaac,
>
> Thanks for volunteering to take up the above tasks.
>
> Myrle, thank you for the needed tips and directions.
>
> Isaac, While you are at it, you might want to go inorder according to the
> dependency graph.
>
> From what I have seen, here is how the order goes:
>
> lang, api, cassandra, mariadb, async, command, test, crypto, anubis,
> service-starter, identity, permitted-feign-client, accounting, customer,
> provisioner, rhythm, office, portfolio, deposit-account-management,
> cheques, teller, payroll, group, reporting.
>
> Where the current project (might) depends on the previous ones. So that the
> builds should not be failing as you move ahead.
>
> So you might want to begin with lang.
>
>
>
> Thanks,
> Awasum
>
>
>
> On Tue, Feb 27, 2018 at 7:34 PM, Myrle Krantz  wrote:
>
> > Hey Isaac,
> >
> > On Tue, Feb 27, 2018 at 3:38 PM, Isaac Kamga 
> > wrote:
> > >> Other places are:
> > >> * the package names
> > >> * a couple of variables in build scripts
> > >> * the copyright notice headers in the source files.
> > >>
> > >
> > > Can I take on these tasks viz updating other places in the code base
> such
> > > as package names, copyright information, etc ?
> >
> > Oh please do.  Can you start with the copyright notices, since that
> > task can done be one repository at a time, and doesn't have
> > cross-repository effects?  A couple of tips while you're doing this:
> > * I suggest doing one repository first, and letting us review it,
> > before doing the rest of the repositories.
> > * In projects without sub-modules, all you'll need to do is change the
> > license section in the build.gradle file.  Then run the license task
> > and it should change all the headers in the project in one step.
> > * In projects with sub-modules, it's kind of the same except that the
> > block of code to change is in the shared.gradle file.
> > * Some projects have "skip existing" set.  You'll have to remove that
> > setting, or the license task won't change anything.
> >
> > I'll not do anything else while you're doing that, since you'll have
> > to touch every file in the repositories, and merges would be required.
> >
> > > I have just sent in a Pull Request
> > >  to the
> > > demo-server repository updating the initial-setup and pull-all scripts
> > for
> > > review.
> >
> > I will review it tomorrow morning (Berlin timezone).  Right now, I'm
> > too tired to properly check code.
> >
> > Best Regards,
> > Myrle
> >
>

Re: Getting started on Fineract CN

[Awasum Yannick]

Hi Isaac,

Thanks for volunteering to take up the above tasks.

Myrle, thank you for the needed tips and directions.

Isaac, While you are at it, you might want to go inorder according to the
dependency graph.

>From what I have seen, here is how the order goes:

lang, api, cassandra, mariadb, async, command, test, crypto, anubis,
service-starter, identity, permitted-feign-client, accounting, customer,
provisioner, rhythm, office, portfolio, deposit-account-management,
cheques, teller, payroll, group, reporting.

Where the current project (might) depends on the previous ones. So that the
builds should not be failing as you move ahead.

So you might want to begin with lang.



Thanks,
Awasum



On Tue, Feb 27, 2018 at 7:34 PM, Myrle Krantz  wrote:

> Hey Isaac,
>
> On Tue, Feb 27, 2018 at 3:38 PM, Isaac Kamga 
> wrote:
> >> Other places are:
> >> * the package names
> >> * a couple of variables in build scripts
> >> * the copyright notice headers in the source files.
> >>
> >
> > Can I take on these tasks viz updating other places in the code base such
> > as package names, copyright information, etc ?
>
> Oh please do.  Can you start with the copyright notices, since that
> task can done be one repository at a time, and doesn't have
> cross-repository effects?  A couple of tips while you're doing this:
> * I suggest doing one repository first, and letting us review it,
> before doing the rest of the repositories.
> * In projects without sub-modules, all you'll need to do is change the
> license section in the build.gradle file.  Then run the license task
> and it should change all the headers in the project in one step.
> * In projects with sub-modules, it's kind of the same except that the
> block of code to change is in the shared.gradle file.
> * Some projects have "skip existing" set.  You'll have to remove that
> setting, or the license task won't change anything.
>
> I'll not do anything else while you're doing that, since you'll have
> to touch every file in the repositories, and merges would be required.
>
> > I have just sent in a Pull Request
> >  to the
> > demo-server repository updating the initial-setup and pull-all scripts
> for
> > review.
>
> I will review it tomorrow morning (Berlin timezone).  Right now, I'm
> too tired to properly check code.
>
> Best Regards,
> Myrle
>

Re: Getting started on Fineract CN

[Myrle Krantz]

Hey Isaac,

On Tue, Feb 27, 2018 at 3:38 PM, Isaac Kamga  wrote:
>> Other places are:
>> * the package names
>> * a couple of variables in build scripts
>> * the copyright notice headers in the source files.
>>
>
> Can I take on these tasks viz updating other places in the code base such
> as package names, copyright information, etc ?

Oh please do.  Can you start with the copyright notices, since that
task can done be one repository at a time, and doesn't have
cross-repository effects?  A couple of tips while you're doing this:
* I suggest doing one repository first, and letting us review it,
before doing the rest of the repositories.
* In projects without sub-modules, all you'll need to do is change the
license section in the build.gradle file.  Then run the license task
and it should change all the headers in the project in one step.
* In projects with sub-modules, it's kind of the same except that the
block of code to change is in the shared.gradle file.
* Some projects have "skip existing" set.  You'll have to remove that
setting, or the license task won't change anything.

I'll not do anything else while you're doing that, since you'll have
to touch every file in the repositories, and merges would be required.

> I have just sent in a Pull Request
>  to the
> demo-server repository updating the initial-setup and pull-all scripts for
> review.

I will review it tomorrow morning (Berlin timezone).  Right now, I'm
too tired to properly check code.

Best Regards,
Myrle

Re: Karma for Creating Boards in JIRA was [Planning Apache Fineract 1.2 Release]

[Myrle Krantz]

On Tue, Feb 27, 2018 at 6:45 PM, Ed Cable  wrote:
> I set up a board and requested permissions to grant other users like Robert
> permission to configure.

Perfect.  Glad someone else picked it up when I dropped it.

: o),
Myrle

Re: Karma for Creating Boards in JIRA was [Planning Apache Fineract 1.2 Release]

[Ed Cable]

I set up a board and requested permissions to grant other users like Robert
permission to configure.

Ed

On Tue, Feb 27, 2018 at 7:43 AM, Ed Cable  wrote:

> Myrle,
>
> I've been continuing to discuss this with Robert and can put in the Infra
> request for the necessary permissions to enable this.
>
> Ed
>
> On Mon, Feb 19, 2018 at 12:52 AM, Myrle Krantz  wrote:
>
>> Hey Robert,
>>
>> We have a jira project for Fineract and for Fineract CN
>>
>> here:
>> https://issues.apache.org/jira/browse/FINERACT
>>
>> and here:
>> https://issues.apache.org/jira/browse/FINCN
>>
>> If you want to put in the effort to create a board for one of these
>> two projects, I'll put in the leg work to figure out what karma you
>> need and how to get it for you.
>>
>> Best Regards,
>> Myrle
>>
>>
>>
>> On Thu, Feb 15, 2018 at 9:52 AM, robert jakech 
>> wrote:
>> > Do we have issue tracker wall i.e story board to track progress of each
>> > task and their statuses?
>> >
>> > On 15 Feb. 2018 6:01 pm, "Nikhil Pawar"  wrote:
>> >
>> >> Hello Devs,
>> >>
>> >> The GLIM/GSIM module which was developed during GSOC 2017 will be sent
>> as
>> >> a new PR by this Sunday.
>> >> I would like to mention that this was developed under guidance of
>> Salton
>> >> Massally from iDT labs.
>> >>
>> >> The PR is open for evaluation by community and feedback/comments are
>> more
>> >> than welcomed!
>> >>
>> >> Regards,
>> >> Nikhil
>> >>
>> >> On Wed, Feb 14, 2018 at 1:41 AM, Ed Cable  wrote:
>> >>
>> >>> That is a great suggestion Phil and of course any synchronous meeting
>> >>> would
>> >>> only complement the discussion on the list and collaboraton on the
>> wiki
>> >>> that we'll be having.
>> >>>
>> >>> Taking up Phil's suggestion, let's begin the discussion on this new
>> thread
>> >>> for planning what should goi into Apache Fineract 1.2. To assist in
>> that
>> >>> I've set up a wiki page at
>> >>> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-
>> >>> +Apache+Fineract
>> >>>
>> >>> Based on what I know others have been working on, here's my take on
>> some
>> >>> of
>> >>> the work that could be included in the release.
>> >>>
>> >>>- GSIM/GLIM Work from Nikhil as part of GSOC
>> >>>- Swagger APIs work done by Sanyam and Chirag
>> >>>- Apache Fineract tasks completed by GCI students.
>> >>>- Changes contributed by Partners including:
>> >>>   - BOWPI Enhancements
>> >>>- Stellar/Fineract integration
>> >>>- Bug Fixes and Minor Enhancements.
>> >>>- PRs from the backlog
>> >>>
>> >>>
>> >>> Let's drive this discussion forward and then a have a synchronous
>> meeting
>> >>> later to hammer out details.
>> >>>
>> >>> Ed
>> >>>
>> >>> On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz 
>> >>> wrote:
>> >>>
>> >>> > On 2/12/18 9:32 AM, Ed Cable wrote:
>> >>> > > Here's the link to screencast from the discussion:
>> >>> > > https://youtu.be/xnTGf4R2s5k
>> >>> > >
>> >>> > > Ed
>> >>> > >
>> >>> > > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable 
>> wrote:
>> >>> > >
>> >>> > >> Hi all,
>> >>> > >>
>> >>> > >> Thanks to Nazeer for leading this session and the sizeable group
>> that
>> >>> > >> attended. Based on the process, we can clearly use the
>> assistance of
>> >>> > other
>> >>> > >> community members in the planning process and committers in the
>> >>> release
>> >>> > >> process so happy we had such good attendance.
>> >>> > >>
>> >>> > >> Based on the discussion, here's a proposal of how timing might
>> look
>> >>> for
>> >>> > >> monthly release cycles with planning (a new phase) starting out
>> six
>> >>> > months
>> >>> > >> prior to the release date.
>> >>> > >>
>> >>> > >> Screencast of session will be posted soon.
>> >>> > >>
>> >>> > >> Please comment on the notes in the table and here's proposed
>> timing
>> >>> for
>> >>> > >> the next 1.2 release:
>> >>> > >>
>> >>> > >> Plans for Release Apache Fineract 1.2
>> >>> > >>
>> >>> > >> Planning Release - Start with a Meeting on Feb 14
>> >>> >
>> >>> > How about starting with a discussion on this list?  Relying on
>> >>> > synchronous meetings cuts out people who can't attend due to time
>> >>> > zones / other commitments.
>> >>> >
>> >>> > Phil
>> >>> > >>
>> >>> > >> Announce Release - Feb 28
>> >>> > >>
>> >>> > >> QA - Feb 28 - March 14
>> >>> > >>
>> >>> > >> Publish Release Notes - March 14
>> >>> > >>
>> >>> > >> Vote on Release - March 21
>> >>> > >>
>> >>> > >> Target release date - March 28
>> >>> > >>
>> >>> > >> Stage
>> >>> > >>
>> >>> > >> Description
>> >>> > >>
>> >>> > >> Proposed Length
>> >>> > >>
>> >>> > >> How Far in Advance of Release (Proposed)
>> >>> > >>
>> >>> > >> How Far in Advance of Release (Currently)
>> >>> > >>
>> >>> > >> Planning of Next Release
>> >>> > >>
>> >>> > >> Discuss with community what would like to ship in next release
>> and
>> >>> what
>> >>> > >> people could work on.
>> >>> > >>
>> >>> > >> Create fix version on JIRA to assign to.
>> >>> > >>
>> >>> > >> Action: modify existing email template to

Re: Planning Apache Fineract 1.2 Release

[Ed Cable]

Myrle,

Thanks for adding that clarity as my initial email was probably confusing.
We are moving to time-driven releases and the initial planning period I
mentioned was to determine which features or work was ready to be
integrated and could be included in the cut-off date for that time-driven
release.

I have set up a scrum board and requested karma to grant Robert access so
he can assist in planning out the next release, Apache Fineract 1.2

Ed

On Wed, Feb 14, 2018 at 4:01 AM, Sendoro Juma  wrote:

> Dear Myrle,
>
> I see your point:
>
> I think primarily we should agree that it is time-driven:
>
> Features listed or to be listed should be taken only as way of making
> focus and pushing for tasks to be completed in-time as per release
> schedule, should they fall short of time... we should move on... with our
> primary commitment which is time.
>
> How about that?
>
> Best Regards
> Sendoro
>
>
>
> - Original Message -
> From: "Myrle Krantz" 
> To: "dev" 
> Sent: Wednesday, February 14, 2018 1:55:03 PM
> Subject: Re: Planning Apache Fineract 1.2 Release
>
> Our release can either be feature-driven or time-driven.  Not both.
> If it's feature-driven, we don't release until the features are in
> there.  If it's time-driven, we release on a certain date, based on
> what's made it in.
>
> Are we in agreement that we wish to make a time-driven release?  Then
> we should be adding a feature to the list for a given release when
> that feature is integrated, and not before.
>
> Best Regards,
> Myrle
>
>
> On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma 
> wrote:
> > Hello Ed,
> >
> > +1 on all you mentioned!
> >
> > I would propose additional point which you have kind of mention it
> already on item related to API Swagger, but just as emphasize
> >
> > - APIs related issues/Enhancements that has been discovered by Mobile or
> Web client application side.
> >
> > This is so,  because we might take longer in addressing issues already
> known from client application side; buy just because of missing visibility;
> > So having this branch in Wiki page will remind us.
> >
> >
> > Best Regards
> >
> > - Original Message -
> > From: "Sendoro Juma" 
> > To: "dev" 
> > Cc: "robertjakech Jakech" 
> > Sent: Wednesday, February 14, 2018 1:38:01 PM
> > Subject: Re: Planning Apache Fineract 1.2 Release
> >
> > Hello Ed,
> >
> > +1 on all mentioned!
> >
> > I would propose additional point which you have kind of mention already
> on API Swagger it, but just as emphasize
> >
> > - APIs related issues/Enhancements that has been discovered by Mobile or
> Web Client Application side.
> >
> > This is so,  because we might take longer in addressing should known
> from client application side by juts because of missing visibility;
> > So having this branch in Wiki page will remind us.
> >
> >
> > Best Regards
> > Sendoro
> >
> >
> >
> > - Original Message -
> > From: "Ed Cable" 
> > To: "dev" , "robertjakech Jakech" <
> robertjak...@gmail.com>
> > Sent: Wednesday, February 14, 2018 9:41:07 AM
> > Subject: Planning Apache Fineract 1.2 Release
> >
> > That is a great suggestion Phil and of course any synchronous meeting
> would
> > only complement the discussion on the list and collaboraton on the wiki
> > that we'll be having.
> >
> > Taking up Phil's suggestion, let's begin the discussion on this new
> thread
> > for planning what should goi into Apache Fineract 1.2. To assist in that
> > I've set up a wiki page at
> > https://cwiki.apache.org/confluence/display/FINERACT/1.
> 2.0+-+Apache+Fineract
> >
> > Based on what I know others have been working on, here's my take on some
> of
> > the work that could be included in the release.
> >
> >- GSIM/GLIM Work from Nikhil as part of GSOC
> >- Swagger APIs work done by Sanyam and Chirag
> >- Apache Fineract tasks completed by GCI students.
> >- Changes contributed by Partners including:
> >   - BOWPI Enhancements
> >- Stellar/Fineract integration
> >- Bug Fixes and Minor Enhancements.
> >- PRs from the backlog
> >
> >
> > Let's drive this discussion forward and then a have a synchronous meeting
> > later to hammer out details.
> >
> > Ed
> >
> > On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz 
> wrote:
> >
> >> On 2/12/18 9:32 AM, Ed Cable wrote:
> >> > Here's the link to screencast from the discussion:
> >> > https://youtu.be/xnTGf4R2s5k
> >> >
> >> > Ed
> >> >
> >> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable  wrote:
> >> >
> >> >> Hi all,
> >> >>
> >> >> Thanks to Nazeer for leading this session and the sizeable group that
> >> >> attended. Based on the process, we can clearly use the assistance of
> >> other
> >> >> community members in the planning process and committers in the
> release
> >> >> process so happy we had such good attendance.
> >> >>
> >> >> Based on the discussion, here's a proposal of how timing might look
> for
> >> >> monthly release cycles with planning (a new phase) starting out six
> >> months
> >> >> prior to t

Re: Updates To How To Build Apache Fineract CN Documentation

[Ed Cable]

Thank you Isaac!

Ed

On Tue, Feb 27, 2018 at 8:33 AM, Isaac Kamga  wrote:

> Hello fineracters,
>
> Trust that you're enjoying the last portions of the month of love!
>
> Given that there's high interest from possible GSoC students and developers
> in contributing to the Apache Fineract CN project ( formerly Mifos I/O ), I
> thought it worthwhile to update the How To Build Fineract CN
>  How+To+Build+Apache+Fineract+CN>
> write-up
> - making it easy,  comprehensive and straightforward so that people have
> the chance to play around with the code bases.
>
> I hope this helps.
>
> At Your Service,
> Isaac Kamga.
>



-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Updates To How To Build Apache Fineract CN Documentation

[Isaac Kamga]

Hello fineracters,

Trust that you're enjoying the last portions of the month of love!

Given that there's high interest from possible GSoC students and developers
in contributing to the Apache Fineract CN project ( formerly Mifos I/O ), I
thought it worthwhile to update the How To Build Fineract CN

write-up
- making it easy,  comprehensive and straightforward so that people have
the chance to play around with the code bases.

I hope this helps.

At Your Service,
Isaac Kamga.

Karma for Creating Boards in JIRA was [Planning Apache Fineract 1.2 Release]

[Ed Cable]

Myrle,

I've been continuing to discuss this with Robert and can put in the Infra
request for the necessary permissions to enable this.

Ed

On Mon, Feb 19, 2018 at 12:52 AM, Myrle Krantz  wrote:

> Hey Robert,
>
> We have a jira project for Fineract and for Fineract CN
>
> here:
> https://issues.apache.org/jira/browse/FINERACT
>
> and here:
> https://issues.apache.org/jira/browse/FINCN
>
> If you want to put in the effort to create a board for one of these
> two projects, I'll put in the leg work to figure out what karma you
> need and how to get it for you.
>
> Best Regards,
> Myrle
>
>
>
> On Thu, Feb 15, 2018 at 9:52 AM, robert jakech 
> wrote:
> > Do we have issue tracker wall i.e story board to track progress of each
> > task and their statuses?
> >
> > On 15 Feb. 2018 6:01 pm, "Nikhil Pawar"  wrote:
> >
> >> Hello Devs,
> >>
> >> The GLIM/GSIM module which was developed during GSOC 2017 will be sent
> as
> >> a new PR by this Sunday.
> >> I would like to mention that this was developed under guidance of Salton
> >> Massally from iDT labs.
> >>
> >> The PR is open for evaluation by community and feedback/comments are
> more
> >> than welcomed!
> >>
> >> Regards,
> >> Nikhil
> >>
> >> On Wed, Feb 14, 2018 at 1:41 AM, Ed Cable  wrote:
> >>
> >>> That is a great suggestion Phil and of course any synchronous meeting
> >>> would
> >>> only complement the discussion on the list and collaboraton on the wiki
> >>> that we'll be having.
> >>>
> >>> Taking up Phil's suggestion, let's begin the discussion on this new
> thread
> >>> for planning what should goi into Apache Fineract 1.2. To assist in
> that
> >>> I've set up a wiki page at
> >>> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-
> >>> +Apache+Fineract
> >>>
> >>> Based on what I know others have been working on, here's my take on
> some
> >>> of
> >>> the work that could be included in the release.
> >>>
> >>>- GSIM/GLIM Work from Nikhil as part of GSOC
> >>>- Swagger APIs work done by Sanyam and Chirag
> >>>- Apache Fineract tasks completed by GCI students.
> >>>- Changes contributed by Partners including:
> >>>   - BOWPI Enhancements
> >>>- Stellar/Fineract integration
> >>>- Bug Fixes and Minor Enhancements.
> >>>- PRs from the backlog
> >>>
> >>>
> >>> Let's drive this discussion forward and then a have a synchronous
> meeting
> >>> later to hammer out details.
> >>>
> >>> Ed
> >>>
> >>> On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz 
> >>> wrote:
> >>>
> >>> > On 2/12/18 9:32 AM, Ed Cable wrote:
> >>> > > Here's the link to screencast from the discussion:
> >>> > > https://youtu.be/xnTGf4R2s5k
> >>> > >
> >>> > > Ed
> >>> > >
> >>> > > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable 
> wrote:
> >>> > >
> >>> > >> Hi all,
> >>> > >>
> >>> > >> Thanks to Nazeer for leading this session and the sizeable group
> that
> >>> > >> attended. Based on the process, we can clearly use the assistance
> of
> >>> > other
> >>> > >> community members in the planning process and committers in the
> >>> release
> >>> > >> process so happy we had such good attendance.
> >>> > >>
> >>> > >> Based on the discussion, here's a proposal of how timing might
> look
> >>> for
> >>> > >> monthly release cycles with planning (a new phase) starting out
> six
> >>> > months
> >>> > >> prior to the release date.
> >>> > >>
> >>> > >> Screencast of session will be posted soon.
> >>> > >>
> >>> > >> Please comment on the notes in the table and here's proposed
> timing
> >>> for
> >>> > >> the next 1.2 release:
> >>> > >>
> >>> > >> Plans for Release Apache Fineract 1.2
> >>> > >>
> >>> > >> Planning Release - Start with a Meeting on Feb 14
> >>> >
> >>> > How about starting with a discussion on this list?  Relying on
> >>> > synchronous meetings cuts out people who can't attend due to time
> >>> > zones / other commitments.
> >>> >
> >>> > Phil
> >>> > >>
> >>> > >> Announce Release - Feb 28
> >>> > >>
> >>> > >> QA - Feb 28 - March 14
> >>> > >>
> >>> > >> Publish Release Notes - March 14
> >>> > >>
> >>> > >> Vote on Release - March 21
> >>> > >>
> >>> > >> Target release date - March 28
> >>> > >>
> >>> > >> Stage
> >>> > >>
> >>> > >> Description
> >>> > >>
> >>> > >> Proposed Length
> >>> > >>
> >>> > >> How Far in Advance of Release (Proposed)
> >>> > >>
> >>> > >> How Far in Advance of Release (Currently)
> >>> > >>
> >>> > >> Planning of Next Release
> >>> > >>
> >>> > >> Discuss with community what would like to ship in next release and
> >>> what
> >>> > >> people could work on.
> >>> > >>
> >>> > >> Create fix version on JIRA to assign to.
> >>> > >>
> >>> > >> Action: modify existing email template to open up planning
> process,
> >>> > >> schedule a meeting to discuss and set a tentative branching date
> >>> (i.e. 2
> >>> > >> weeks later, if release date is a month past that).
> >>> > >>
> >>> > >> .
> >>> > >>
> >>> > >> 1 week
> >>> > >>
> >>> > >> 6 weeks
> >>> > >>
> >>> > >> Doesn’t Exist
> >>> > >>
> >>> > >> Announcemen

Re: Planning Apache Fineract 1.2 Release

[Ed Cable]

Hello Pari,

Thanks for your email. You can browse the list of project that the Mifos
Initiative mentors will be overseeing for Google Summer of Code at
https://mifosforge.jira.com/wiki/spaces/RES/pages/
225411076/Google+Summer+of+Code+2018+Ideas

It will include both project that are related to the Apache Fineract
platform as well as projects related to the Mifos X web and mobile apps.

Please browse that list there which has links to all the repos and issue
trackers.

For good beginners issues related to Apache Fineract, please browse:
https://goo.gl/f5NgHy

Welcome!

Ed

On Mon, Feb 19, 2018 at 8:34 AM, Pari Tiwari 
wrote:

> Hello,
> Myself Pari Tiwari
> So actually I am very new to Mifos initiative  and it's projects. So can
> you please tell me what I can do for mifos initiative and how can I learn
> about all the tasks and projects of mifos.
> Eager to learn.
> Kindly reply
> Thank you
>
> On 19 Feb 2018 8:53 p.m., "Sendoro Juma"  wrote:
>
> > Hello Sharan,
> >
> > +1
> > The JIRA voting system should be fully be utilized by us as community! As
> > part even of raising criticality!
> >
> > Cheers
> > Sendoro
> >
> > - Original Message -
> > From: "Sharan F" 
> > To: "dev" 
> > Sent: Monday, February 19, 2018 4:25:38 PM
> > Subject: Re: Planning Apache Fineract 1.2 Release
> >
> > Hi All
> >
> > I know that in Jira you can vote for an issue (so can keep a tally of
> > which issues people see as important or want the project to implement).
> > In the existing JIra default setup there is a task type called 'Wish' so
> > maybe that could be used to capture ideas or wishes.
> >
> > Thanks
> > Sharan
> >
> > I know that Jira is setup to allow people to vote on specific issues
> >
> > On 19/02/18 14:44, Ed Cable wrote:
> > > Thanks Myrle for sharing those links to clarify the Apache tools
> > available
> > > and helping get Robert the karma to configure the necessary boards.
> > Robert,
> > > that would be a super valuable contribution that you could make
> > leveraging
> > > your skillset  and expertise around agile development to assist the
> > > community with releases of Fineract 1.x and roadmapping for Fineract
> CN.
> > >
> > > Myrle and others, do you know if Apache offers any tools for idea
> > tracking
> > > and voting like https://www.aha.io/product/features/ideas#tour-nav. In
> > > conversations for some other volunteers, we thought this might be a
> nice
> > > lightweight tool to capture high level and gauge input from a broad
> range
> > > of stakeholders to feed into a roadmap.
> > >
> > > Ed
> > >
> > > On Feb 19, 2018 03:52, "Myrle Krantz"  wrote:
> > >
> > >> Hey Robert,
> > >>
> > >> We have a jira project for Fineract and for Fineract CN
> > >>
> > >> here:
> > >> https://issues.apache.org/jira/browse/FINERACT
> > >>
> > >> and here:
> > >> https://issues.apache.org/jira/browse/FINCN
> > >>
> > >> If you want to put in the effort to create a board for one of these
> > >> two projects, I'll put in the leg work to figure out what karma you
> > >> need and how to get it for you.
> > >>
> > >> Best Regards,
> > >> Myrle
> > >>
> > >>
> > >>
> > >> On Thu, Feb 15, 2018 at 9:52 AM, robert jakech <
> robertjak...@gmail.com>
> > >> wrote:
> > >>> Do we have issue tracker wall i.e story board to track progress of
> each
> > >>> task and their statuses?
> > >>>
> > >>> On 15 Feb. 2018 6:01 pm, "Nikhil Pawar"  wrote:
> > >>>
> >  Hello Devs,
> > 
> >  The GLIM/GSIM module which was developed during GSOC 2017 will be
> sent
> > >> as
> >  a new PR by this Sunday.
> >  I would like to mention that this was developed under guidance of
> > Salton
> >  Massally from iDT labs.
> > 
> >  The PR is open for evaluation by community and feedback/comments are
> > >> more
> >  than welcomed!
> > 
> >  Regards,
> >  Nikhil
> > 
> >  On Wed, Feb 14, 2018 at 1:41 AM, Ed Cable 
> wrote:
> > 
> > > That is a great suggestion Phil and of course any synchronous
> meeting
> > > would
> > > only complement the discussion on the list and collaboraton on the
> > wiki
> > > that we'll be having.
> > >
> > > Taking up Phil's suggestion, let's begin the discussion on this new
> > >> thread
> > > for planning what should goi into Apache Fineract 1.2. To assist in
> > >> that
> > > I've set up a wiki page at
> > > https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-
> > > +Apache+Fineract
> > >
> > > Based on what I know others have been working on, here's my take on
> > >> some
> > > of
> > > the work that could be included in the release.
> > >
> > > - GSIM/GLIM Work from Nikhil as part of GSOC
> > > - Swagger APIs work done by Sanyam and Chirag
> > > - Apache Fineract tasks completed by GCI students.
> > > - Changes contributed by Partners including:
> > >- BOWPI Enhancements
> > > - Stellar/Fineract integration
> > > - Bug Fixes 

Re: Getting started on Fineract CN

[Isaac Kamga]

Hi Myrle,

On Mon, Feb 26, 2018 at 6:48 PM, Myrle Krantz  wrote:

> Hey Phil,
>
> Thanks for the feedback.  I've just updated the artifact ids to apache
> fineract.  It's not the only place we need to replace Mifos with
> Apache Fineract though.
>
> Other places are:
> * the package names
> * a couple of variables in build scripts
> * the copyright notice headers in the source files.
>

Can I take on these tasks viz updating other places in the code base such
as package names, copyright information, etc ?

I have just sent in a Pull Request
 to the
demo-server repository updating the initial-setup and pull-all scripts for
review.


> On that last point I have a question which you are probably a good
> person to ask: Can I just replace Mifos and Kuelap with Apache?  Or we
> need to do something more complicated there.
>
> In the mean time, and with apologies, I strongly suggest you repull
> all the fineract repositories so that you are working with up-to-date
> artifact ids.
>
> Best Regards,
> Myrle
>
>
At Your Service,
isaac Kamga.

>
>
> On Mon, Feb 26, 2018 at 6:25 PM, Phil Steitz 
> wrote:
> > On 2/26/18 12:52 AM, Markus Geiss wrote:
> >> Hey Phil,
> >>
> >> given all repos got pushed as is, I guess one of the first tasks is to
> >> rename
> >> all packages and projects to fit into the Apache layout.
> >>
> >> If you just want to get started now, you need to call
> >>
> >>   ./gradelw publishToMavenLocal (assuming a *nix OS)
> >>
> >> for every project. You should be able to adjust and run the
> >> initial setup script found at the demo-server.
> >
> > Thanks, Markus.  I have started just doing the installs using the
> > mifos packaging.  Once I get that working, I will start working on a
> > repackaging PR.
> >
> > Phil
> >>
> >> Cheers
> >>
> >> Markus
> >>
> >> .::Yagni likes a DRY KISS::.
> >>
> >> On Sun, Feb 25, 2018 at 10:18 PM Phil Steitz 
> wrote:
> >>
> >>> I would like to start contributing to CN.  I have cloned all of the
> >>> repos and thought it would be a good first step to build the
> >>> demo-server.  The readme for that component says that as a
> >>> precondition, "All Mifos I/O projects must be published to your
> >>> local Maven repository."  I assume that now means some subset of all
> >>> of the fineract-cn components.   But in build.gradle, I see
> >>> references to mifos components.  Do I maybe need to just replace
> >>> these with the fineract-cn versions and install these locally using
> >>> "gradle publisToMavenLocal" from each of these repos?
> >>>
> >>> I am happy to provide doco and config patches as I get this working
> >>> if I can get pointed in the right direction.   Thanks in advance!
> >>>
> >>> Phil
> >>>
> >>>
> >
>

Re: Web-self-service-app

[Chirag Gupta]

Hello,

I think that this data is coming from the API. The server is demo.openmf.org
.

Hope this Helps :)

Regards,
Chirag Gupta

On Tue, Feb 27, 2018 at 7:06 PM, Mexina Daniel  wrote:

> Hello
>
> I see when i "gulp serve" the web-self-service-app cloned from
> https://github.com/openMF/web-self-service-app, it run with url
> http://localhost:3000/
>
> What server does these data come from?, and how about if i want to access
> from my server?
>
> Thanks in advance
>
> --
> Mexina M Daniel
> Lead Software Developer
> Research & Development
>
> Office: +255 22 261 8511 | Mobile: +255 712 110 791
>
> Singo Africa Limited
> Block G, Mbezi Beach B | 7Nakawale Road | P.O BOX 78908 | 14121 Dar es
> salaam
>
> singo.africa | amala.co.tz
>
> Let's grow together
>

Web-self-service-app

[Mexina Daniel]

Hello 

I see when i "gulp serve" the web-self-service-app cloned from 
https://github.com/openMF/web-self-service-app, it run with url 
http://localhost:3000/ 

What server does these data come from?, and how about if i want to access from 
my server? 

Thanks in advance 

-- 
Mexina M Daniel 
Lead Software Developer 
Research & Development 

Office: +255 22 261 8511 | Mobile: +255 712 110 791 

Singo Africa Limited 
Block G, Mbezi Beach B | 7Nakawale Road | P.O BOX 78908 | 14121 Dar es 
salaam 

singo.africa | amala.co.tz 

Let's grow together 

Re: GSoC 2018: Fineract CN SMS & Email Notifications

[Isaac Kamga]

Hi Viswa,

You're free to go ahead and send a PR to get this added to demo-server.

More grease to your elbows.

At Your Service,
Isaac Kamga

On Tue, Feb 27, 2018 at 1:58 PM, Viswa Ramamoorthy <
viswaramamoor...@yahoo.com.invalid> wrote:

> For infrastructure dependencies, it is better to go with Docker and have
> it externalized. A YAML file with docker compose construct can be used to
> bring up dependencies like AciveMQ, DB and Eureka.
> In MAC, linux, Windows 10 Docker runs as daemon/back ground process.
> Windows 7 would need additional steps get Docker working.
> This can give better visibility on infrastructure.
> I can send PR to get this added for demo server
>
> Sent from Yahoo Mail on Android
>
>   On Tue, Feb 27, 2018 at 6:37 AM, Acha Bill
> wrote:   Hello,
>
> I still get these errors for different services when running the demo
> server
> E00:19:59.235 [DefaultMessageListenerContainer-3] ERROR o.s.j.l.
> DefaultMessageListenerContainer - Could not refresh JMS Connection for
> destination 'payroll-v1' - retrying using FixedBackOff{interval=5000,
> currentAttempts=0, maxAttempts=unlimited}. Cause: Error while attempting to
> retrieve a connection from the pool; nested exception is
> javax.jms.JMSException: Could not connect to broker URL:
> tcp://localhost:61616. Reason: java.net.ConnectException: Connection
> refused (Connection refused)
>
> Viswa suggested that I needed to separately run Active MQ but I’ve not
> done that route since you said…
> > if you run the demo-server locally it will start Eureka, ActiveMQ,
> MariaDB, and Apache Cassandra
> > embedded, so no need to install it.
>
> I’m running Mac of with 8GB RAM and i5 Dual core.
> I’ve even tried setting the timeout for the event recorder to, 999_999 and
> it still gives the same errors.
>
> If I go with running ActiveMQ externally before starting the server, it
> runs and ends at multiple lines of -
> [AsyncResolver-bootstrap-executor-0] INFO  c.n.d.s.r.aws.ConfigClusterResolver
> - Resolving eureka endpoints via configuration
> I don’t know if this is the expected end.
>
> Now, if I try to login on the web app with a wrong tenant, say “bill”,
> this is what I get on the console,
> [qtp392918519-21] INFO  i.m.c.l.c.ServiceExceptionFilter - Responding
> with a service error ServiceError{code=404, message='Tenant [bill]
> unknown.'}
> Which gives me the impression that everything is running fine.
>
> So now if I try to login with the right tenant - “playground”, it does not
> show anything on the console and shows "Sorry, that login did not work.” On
> the web app.
>
> I’ll be grateful for any more guiltiness in resolving these.
>
> > On Feb 26, 2018, at 9:01 AM, Markus Geiss  wrote:
> >
> > Hey all,
> >
> > if you run the demo-server locally it will start Eureka, ActiveMQ,
> MariaDB, and Apache Cassandra
> > embedded, so no need to install it.
> >
> > The whole setup is very resource hungry, given we run all datastores and
> all micrsoervices at once.
> > You'd need at least 8GB RAM and a good CPU. If this is not the case on
> your machine, you can try
> > to adjust the timeout used for the EventRecorder to fit the slower
> startup behavior.You can find
> > the configuration at ServiceRunner.java in the demo-server
> >
> >@EnableEventRecording(maxWait = 120_000) // (120 is the default)
> >
> > Cheers
> >
> > Markus
> >
> > .::Yagni likes a DRY KISS::.
> >
> > On Mon, Feb 26, 2018 at 8:18 AM Piyadassi Shakya <
> shakyapiyada...@gmail.com > wrote:
> > Hi Awasum
> >  I followed your points yet again I am facing the same error and it says
> > package.json not found.
> >
> >
> >
> > With Regards
> > Piyadassi
> >
> >
> > On Mon, Feb 26, 2018 at 6:34 AM, Viswa Ramamoorthy <
> > viswaramamoor...@yahoo.com .invalid>
> wrote:
> >
> > >  First error - cannot connect to tcp://localhost:61616 - is ActiveMQ
> > > related. Is activeMQ running in localhost? You can related to ActiveMQ
> setup
> > > Second error indicates that the microservices are looking for Netflix
> > > Eureka server to register to. I do not see any mention of Eureka server
> > > setup in the readme of Fineract CN demo server. However, if you setup a
> > > Eureka server that running at localhost 8761 port (note default port is
> > > 8761), it would work.
> > >
> > >On ‎Sunday‎, ‎February‎ ‎25‎, ‎2018‎ ‎04‎:‎31‎:‎19‎ ‎PM‎ ‎EST, Acha
> > > Bill mailto:achabil...@gmail.com>> wrote:
> > >
> > >  In running the demo server, java -Ddemoserver.provision=true -jar
> > > demo-server-0.1.0-BUILD-SNAPSHOT.jar
> > > I get these errors from different services:
> > >
> > > [DefaultMessageListenerContainer-1] ERROR o.s.j.l.
> > > DefaultMessageListenerContainer - Could not refresh JMS Connection for
> > > destination 'identity-v1' - retrying using FixedBackOff{interval=5000,
> > > currentAttempts=0, maxAttempts=unlimited}. Cause: Error while
> attempting to
> > > retrieve a connection from the pool; nested exception i

Re: GSoC 2018: Fineract CN SMS & Email Notifications

[Viswa Ramamoorthy]

For infrastructure dependencies, it is better to go with Docker and have it 
externalized. A YAML file with docker compose construct can be used to bring up 
dependencies like AciveMQ, DB and Eureka.
In MAC, linux, Windows 10 Docker runs as daemon/back ground process. Windows 7 
would need additional steps get Docker working.
This can give better visibility on infrastructure. 
I can send PR to get this added for demo server

Sent from Yahoo Mail on Android 
 
  On Tue, Feb 27, 2018 at 6:37 AM, Acha Bill wrote:   
Hello,

I still get these errors for different services when running the demo server
E00:19:59.235 [DefaultMessageListenerContainer-3] ERROR 
o.s.j.l.DefaultMessageListenerContainer - Could not refresh JMS Connection for 
destination 'payroll-v1' - retrying using FixedBackOff{interval=5000, 
currentAttempts=0, maxAttempts=unlimited}. Cause: Error while attempting to 
retrieve a connection from the pool; nested exception is 
javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. 
Reason: java.net.ConnectException: Connection refused (Connection refused)

Viswa suggested that I needed to separately run Active MQ but I’ve not done 
that route since you said…
> if you run the demo-server locally it will start Eureka, ActiveMQ, MariaDB, 
> and Apache Cassandra
> embedded, so no need to install it.

I’m running Mac of with 8GB RAM and i5 Dual core.
I’ve even tried setting the timeout for the event recorder to, 999_999 and it 
still gives the same errors.

If I go with running ActiveMQ externally before starting the server, it runs 
and ends at multiple lines of - 
[AsyncResolver-bootstrap-executor-0] INFO  c.n.d.s.r.aws.ConfigClusterResolver 
- Resolving eureka endpoints via configuration
I don’t know if this is the expected end.

Now, if I try to login on the web app with a wrong tenant, say “bill”, this is 
what I get on the console,
[qtp392918519-21] INFO  i.m.c.l.c.ServiceExceptionFilter - Responding with a 
service error ServiceError{code=404, message='Tenant [bill] unknown.'}
Which gives me the impression that everything is running fine.

So now if I try to login with the right tenant - “playground”, it does not show 
anything on the console and shows "Sorry, that login did not work.” On the web 
app.

I’ll be grateful for any more guiltiness in resolving these.

> On Feb 26, 2018, at 9:01 AM, Markus Geiss  wrote:
> 
> Hey all,
> 
> if you run the demo-server locally it will start Eureka, ActiveMQ, MariaDB, 
> and Apache Cassandra
> embedded, so no need to install it.
> 
> The whole setup is very resource hungry, given we run all datastores and all 
> micrsoervices at once.
> You'd need at least 8GB RAM and a good CPU. If this is not the case on your 
> machine, you can try
> to adjust the timeout used for the EventRecorder to fit the slower startup 
> behavior.You can find
> the configuration at ServiceRunner.java in the demo-server
> 
>    @EnableEventRecording(maxWait = 120_000) // (120 is the default)
> 
> Cheers
> 
> Markus
> 
> .::Yagni likes a DRY KISS::.
> 
> On Mon, Feb 26, 2018 at 8:18 AM Piyadassi Shakya  > wrote:
> Hi Awasum
>  I followed your points yet again I am facing the same error and it says
> package.json not found.
> 
> 
> 
> With Regards
> Piyadassi
> 
> 
> On Mon, Feb 26, 2018 at 6:34 AM, Viswa Ramamoorthy <
> viswaramamoor...@yahoo.com .invalid> wrote:
> 
> >  First error - cannot connect to tcp://localhost:61616 - is ActiveMQ
> > related. Is activeMQ running in localhost? You can related to ActiveMQ setup
> > Second error indicates that the microservices are looking for Netflix
> > Eureka server to register to. I do not see any mention of Eureka server
> > setup in the readme of Fineract CN demo server. However, if you setup a
> > Eureka server that running at localhost 8761 port (note default port is
> > 8761), it would work.
> >
> >    On ‎Sunday‎, ‎February‎ ‎25‎, ‎2018‎ ‎04‎:‎31‎:‎19‎ ‎PM‎ ‎EST, Acha
> > Bill mailto:achabil...@gmail.com>> wrote:
> >
> >  In running the demo server, java -Ddemoserver.provision=true -jar
> > demo-server-0.1.0-BUILD-SNAPSHOT.jar
> > I get these errors from different services:
> >
> > [DefaultMessageListenerContainer-1] ERROR o.s.j.l.
> > DefaultMessageListenerContainer - Could not refresh JMS Connection for
> > destination 'identity-v1' - retrying using FixedBackOff{interval=5000,
> > currentAttempts=0, maxAttempts=unlimited}. Cause: Error while attempting to
> > retrieve a connection from the pool; nested exception is
> > javax.jms.JMSException: Could not connect to broker URL:
> > tcp://localhost:61616. Reason: java.net.ConnectException: Connection
> > refused (Connection refused)
> >
> >
> > And finally terminates with:
> >
> > Time: 1,456.026
> > There was 1 failure:
> > 1) startDevServer(io.mifos.dev.ServiceRunner)
> > java.lang.AssertionError
> >        at org.junit.Assert.fail(Assert.java:86)
> >        at org.junit.Assert.assertTrue(Asser

Re: GSoC 2018: Fineract CN SMS & Email Notifications

[Acha Bill]

Hello,

I still get these errors for different services when running the demo server
E00:19:59.235 [DefaultMessageListenerContainer-3] ERROR 
o.s.j.l.DefaultMessageListenerContainer - Could not refresh JMS Connection for 
destination 'payroll-v1' - retrying using FixedBackOff{interval=5000, 
currentAttempts=0, maxAttempts=unlimited}. Cause: Error while attempting to 
retrieve a connection from the pool; nested exception is 
javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. 
Reason: java.net.ConnectException: Connection refused (Connection refused)

Viswa suggested that I needed to separately run Active MQ but I’ve not done 
that route since you said…
> if you run the demo-server locally it will start Eureka, ActiveMQ, MariaDB, 
> and Apache Cassandra
> embedded, so no need to install it.

I’m running Mac of with 8GB RAM and i5 Dual core.
I’ve even tried setting the timeout for the event recorder to, 999_999 and it 
still gives the same errors.

If I go with running ActiveMQ externally before starting the server, it runs 
and ends at multiple lines of - 
[AsyncResolver-bootstrap-executor-0] INFO  c.n.d.s.r.aws.ConfigClusterResolver 
- Resolving eureka endpoints via configuration
I don’t know if this is the expected end.

Now, if I try to login on the web app with a wrong tenant, say “bill”, this is 
what I get on the console,
[qtp392918519-21] INFO  i.m.c.l.c.ServiceExceptionFilter - Responding with a 
service error ServiceError{code=404, message='Tenant [bill] unknown.'}
Which gives me the impression that everything is running fine.

So now if I try to login with the right tenant - “playground”, it does not show 
anything on the console and shows "Sorry, that login did not work.” On the web 
app.

I’ll be grateful for any more guiltiness in resolving these.

> On Feb 26, 2018, at 9:01 AM, Markus Geiss  wrote:
> 
> Hey all,
> 
> if you run the demo-server locally it will start Eureka, ActiveMQ, MariaDB, 
> and Apache Cassandra
> embedded, so no need to install it.
> 
> The whole setup is very resource hungry, given we run all datastores and all 
> micrsoervices at once.
> You'd need at least 8GB RAM and a good CPU. If this is not the case on your 
> machine, you can try
> to adjust the timeout used for the EventRecorder to fit the slower startup 
> behavior.You can find
> the configuration at ServiceRunner.java in the demo-server
> 
> @EnableEventRecording(maxWait = 120_000) // (120 is the default)
> 
> Cheers
> 
> Markus
> 
> .::Yagni likes a DRY KISS::.
> 
> On Mon, Feb 26, 2018 at 8:18 AM Piyadassi Shakya  > wrote:
> Hi Awasum
>  I followed your points yet again I am facing the same error and it says
> package.json not found.
> 
> 
> 
> With Regards
> Piyadassi
> 
> 
> On Mon, Feb 26, 2018 at 6:34 AM, Viswa Ramamoorthy <
> viswaramamoor...@yahoo.com .invalid> wrote:
> 
> >  First error - cannot connect to tcp://localhost:61616 - is ActiveMQ
> > related. Is activeMQ running in localhost? You can related to ActiveMQ setup
> > Second error indicates that the microservices are looking for Netflix
> > Eureka server to register to. I do not see any mention of Eureka server
> > setup in the readme of Fineract CN demo server. However, if you setup a
> > Eureka server that running at localhost 8761 port (note default port is
> > 8761), it would work.
> >
> > On ‎Sunday‎, ‎February‎ ‎25‎, ‎2018‎ ‎04‎:‎31‎:‎19‎ ‎PM‎ ‎EST, Acha
> > Bill mailto:achabil...@gmail.com>> wrote:
> >
> >  In running the demo server, java -Ddemoserver.provision=true -jar
> > demo-server-0.1.0-BUILD-SNAPSHOT.jar
> > I get these errors from different services:
> >
> > [DefaultMessageListenerContainer-1] ERROR o.s.j.l.
> > DefaultMessageListenerContainer - Could not refresh JMS Connection for
> > destination 'identity-v1' - retrying using FixedBackOff{interval=5000,
> > currentAttempts=0, maxAttempts=unlimited}. Cause: Error while attempting to
> > retrieve a connection from the pool; nested exception is
> > javax.jms.JMSException: Could not connect to broker URL:
> > tcp://localhost:61616. Reason: java.net.ConnectException: Connection
> > refused (Connection refused)
> >
> >
> > And finally terminates with:
> >
> > Time: 1,456.026
> > There was 1 failure:
> > 1) startDevServer(io.mifos.dev.ServiceRunner)
> > java.lang.AssertionError
> > at org.junit.Assert.fail(Assert.java:86)
> > at org.junit.Assert.assertTrue(Assert.java:41)
> > at org.junit.Assert.assertTrue(Assert.java:52)
> > at io.mifos.dev.ServiceRunner.provisionApp(ServiceRunner.java:484)
> > at io.mifos.dev.ServiceRunner.provisionAppsViaSeshatForTenan
> > t(ServiceRunner.java:442)
> > at io.mifos.dev.ServiceRunner.provisionAppsViaSeshat(
> > ServiceRunner.java:358)
> > at io.mifos.dev.ServiceRunner.startDevServer(ServiceRunner.
> > java:260)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > 

Re: Reverse Account Transfer

[Mexina Daniel]

Hello Zayyad 

You can create an issue in Jira 

Regards 


From: "zayyad"  
To: "Mexina Daniel"  
Cc: "dev"  
Sent: Tuesday, February 27, 2018 10:31:51 AM 
Subject: Reverse Account Transfer 



Yes Mexina, 



We get the same exception. 



I don’t see any business logic in blocking transfer reversals. 



Definitely, an enhancement is needed. 




Regards; 



*** 

Zayyad A. Said | Chairman & C.E.O 



Cell No.: +254 716 615274 | Skype: zsaid2011 

Email: [ mailto:zay...@intrasofttechnologies.com | 
zay...@intrasofttechnologies.com ] 









From: Mexina Daniel [mailto:mexina@singo.africa] 
Sent: 27 February 2018 10:26 AM 
To: dev  
Cc: mifos-developer ; 
zay...@intrasofttechnologies.com 
Subject: Re: Reverse Account Transfer 





Hello Zayyad 





It seems in the system there is an exception handled when someone tries to 
reverse the transaction of fund transfer ( See picture attached ) 





Someone can help to clarify if there is a business logic for this 





Regards 



From: "Zayyad A. Said" < [ mailto:zay...@intrasofttechnologies.com | 
zay...@intrasofttechnologies.com ] > 
To: "dev" < [ mailto:dev@fineract.apache.org | dev@fineract.apache.org ] >, 
"mifos-developer" < [ mailto:mifos-develo...@lists.sourceforge.net | 
mifos-develo...@lists.sourceforge.net ] > 
Sent: Tuesday, February 27, 2018 10:09:01 AM 
Subject: Reverse Account Transfer 





Hello Devs, 



We seem not to be able to reverse transfer transactions i.e. from savings to 
loan accounts. 



Are we the only one experiencing this or this is a bug that needs to be 
addressed? 



Kindly advise what solution we can possibly have to be able to reverse 
transfers. 



Regards; 



*** 

Zayyad A. Said | Chairman & C.E.O 



Cell No.: +254 716 615274 | Skype: zsaid2011 

Email: [ mailto:zay...@intrasofttechnologies.com | 
zay...@intrasofttechnologies.com ] 













-- 


Mexina M Daniel 
Lead Software Developer 
Research & Development 

Office: +255 22 261 8511 | Mobile: +255 712 110 791 

Singo Africa Limited 
Block G, Mbezi Beach B | 7Nakawale Road | P.O BOX 78908 | 14121 Dar es 
salaam 

singo.africa | amala.co.tz 

Let's grow together 


-- 
Mexina M Daniel 
Lead Software Developer 
Research & Development 

Office: +255 22 261 8511 | Mobile: +255 712 110 791 

Singo Africa Limited 
Block G, Mbezi Beach B | 7Nakawale Road | P.O BOX 78908 | 14121 Dar es 
salaam 

singo.africa | amala.co.tz 

Let's grow together