Re: [GNC-dev] About Gnucash

2020-02-18 Thread John Ralls
It is easy: Just look at 
https://github.com/Gnucash/gnucash-on-flatpak/blob/master/modules/aqbanking.json.
 There's a history button on the right side near the top that you can use to 
look back to when your flatpak was built.

Regards,
John Ralls


> On Feb 18, 2020, at 4:29 PM, Chris Graves  wrote:
> 
> Hi Frank,
> Thanks for the tip, I recently learned of the aqbanking-cli command and have 
> been searching for a guide on it's use.  From what I've found (or not), looks 
> like I'll have to review the source code.
> 
> Also, with all the recent issues with AQB for both HBCI and OFX users, I was 
> thinking that it would be nice to have quick, easy access to it's version 
> info.  Not so easy/obvious from a flatpak install unless I'm missing 
> something (though I have found how to access it).
> 
> Chris
> 
> On Mon, Feb 17, 2020 at 8:30 PM Frank H. Ellenberger 
>  wrote:
> To get the important versions of Aqbanking and it's helper library
> Gwenhywfar, you can enter the command
>  aqbanking-cli versions
> 
> Regards
> Frank
> 
> Am 18.02.20 um 04:45 schrieb John Ralls:
> > 
> > 
> >> On Feb 17, 2020, at 4:26 PM, chris graves  wrote:
> >>
> >> On the About GnuCash window, is displayed among other things
> >> Version
> >> Build ID
> >> Finance::Quote
> >>
> >> Question, should the AQBanking version be displayed as well?  Or perhaps 
> >> is this just opening up a whole can of worms for all included third party 
> >> s/w?
> > 
> > Not really a can of worms, but not really necessary because unless the user 
> > is building dependencies themselves we can pretty easily find out what 
> > version of any dependency they've got: We build the Mac and Windows bundles 
> > ourselves and https://repology.org will tell us pretty quickly what version 
> > of any dependency goes with any distro. 
> > 
> > Finance::Quote is a bit different because it's so easily obtained/upgraded 
> > from CPAN that a lot of users won't have what's in their distros; it's also 
> > installed outside of the Windows and Mac bundles.
> > 
> > Regards,
> > John Ralls
> 

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: [GNC-dev] [GNC] Fwd: Failed - import of QIF files from Quicken

2020-02-18 Thread Adrien Monteleone
I seem to recall a development goal being to eliminate Scheme code except for 
reports.

This might be a good candidate for just re-writing this in C/C++ with proper 
tests and verbose error output and/or logging.

If someone with the skillset is interested of course.

Regards,
Adrien

> On Feb 18, 2020 w8d49, at 6:35 PM, James Peterson  wrote:
> 
> Well, with no hint of what the problem is, even smaller
> test sets won't necessarily find anything, so it could be 
> a lot of work for no benefit.  For example, I could export
> each account separately (although there are about 80 of them
> so that's a lot of work), and each account could load 
> okay separately, because maybe the problem is an interaction 
> between two different accounts. So then I have to do 80*79
> possible pairs of accounts, and so on.
> 
> My poking around in the 
> source code to try to find the problem suggests that the
> problem is in the Scheme part that seems to be working with
> all the accounts at the same time:
> 
> ;; Build a local account tree to hold converted transactions.
> 
> ;; Sort the account list on the depth of the account path.
> 
> ;; Make all the accounts.
> 
> ;; Run through the markable transactions marking any
>  ;; duplicates.  marked transactions/splits won't get imported.
> 
>   ;; Convert into a GnuCash transaction.
>   ;; rebalance and commit everything
> 
> So this looks like multiple runs thru the data, and even printing
> the line number won't narrow it down -- you have to know what
> step of the process we are doing, and where we are in the data
> at that point.
> 
> As things stand, we don't even know what the immediate problem
> is -- a divide by zero?  Looking for an account that should exist,
> but doesn't?, an account type that it doesn't know about? 
> 
> The code is not written to allow it to even explain what it is
> doing. If we are going to use this code base, someone who actually
> understands, and is comfortable with the code will need to add
> a "verbose input processing" level or something that will create
> a log file explaining what it is going to try to do, then do it,
> then explain what it got and how it interprets that. I've done 
> that with code before, but only C code, where, if need be, there is
> the equivalent of a printf to a log file between every major step,
> or each iteration of a loop, explaining what it thinks it is doing
> and with what input and with what result.  I just don't know how to
> add that to scheme.
> 
> jim

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: [GNC-dev] About Gnucash

2020-02-18 Thread Chris Graves
Hi Frank,
Thanks for the tip, I recently learned of the aqbanking-cli command and
have been searching for a guide on it's use.  From what I've found (or
not), looks like I'll have to review the source code.

Also, with all the recent issues with AQB for both HBCI and OFX users, I
was thinking that it would be nice to have quick, easy access to it's
version info.  Not so easy/obvious from a flatpak install unless I'm
missing something (though I have found how to access it).

Chris

On Mon, Feb 17, 2020 at 8:30 PM Frank H. Ellenberger <
frank.h.ellenber...@gmail.com> wrote:

> To get the important versions of Aqbanking and it's helper library
> Gwenhywfar, you can enter the command
>  aqbanking-cli versions
>
> Regards
> Frank
>
> Am 18.02.20 um 04:45 schrieb John Ralls:
> >
> >
> >> On Feb 17, 2020, at 4:26 PM, chris graves 
> wrote:
> >>
> >> On the About GnuCash window, is displayed among other things
> >> Version
> >> Build ID
> >> Finance::Quote
> >>
> >> Question, should the AQBanking version be displayed as well?  Or
> perhaps is this just opening up a whole can of worms for all included third
> party s/w?
> >
> > Not really a can of worms, but not really necessary because unless the
> user is building dependencies themselves we can pretty easily find out what
> version of any dependency they've got: We build the Mac and Windows bundles
> ourselves and https://repology.org will tell us pretty quickly what
> version of any dependency goes with any distro.
> >
> > Finance::Quote is a bit different because it's so easily
> obtained/upgraded from CPAN that a lot of users won't have what's in their
> distros; it's also installed outside of the Windows and Mac bundles.
> >
> > Regards,
> > John Ralls
>
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: [GNC-dev] [GNC] Failed - import of QIF files from Quicken

2020-02-18 Thread Adrien Monteleone
Tom, info about sources and building can be found on the GnuCash website and 
wiki. Check the Development section.

Regards,
Adrien

> On Tue, 18 Feb 2020 at 15:51, Tom Hatzigeorgiou  wrote:
> 
>> To do this someone will need to help me.
>> I don't know how projects like this work.
>> I have no idea where the program source exists and the tools I will need
>> to manipulate it.
>> 
>> I was thinking that a very simple way to debug the code is, for someone to
>> place a display on a version of the new importer where every record that it
>> processes gets displayed (in a log file) before it gets imported.
>> This way by running the importer I will see at what record(s) it failed.
>> I would run it multiple times until I find and eliminate ALL the records
>> of my file that it fails on.
>> When all bad records get eliminated and my file gets loaded correctly by
>> the current importer, I don't think I would have a problem sending you all
>> those bad records for you to analyze and see where the new importer has
>> gone bad.
>> 
>> DO you think something like the above can be done?

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: [GNC-dev] [GNC] Failed - import of QIF files from Quicken

2020-02-18 Thread Frank H. Ellenberger



Am 18.02.20 um 22:52 schrieb Christopher Lam:
> Sorry. Please ask other devs on public mailing list.
> 
> On Tue, 18 Feb 2020 at 15:51, Tom Hatzigeorgiou  wrote:
> 
>> To do this someone will need to help me.
>> I don't know how projects like this work.
>> I have no idea where the program source exists and the tools I will need
>> to manipulate it.
>>
>> I was thinking that a very simple way to debug the code is, for someone to
>> place a display on a version of the new importer where every record that it
>> processes gets displayed (in a log file) before it gets imported.
>> This way by running the importer I will see at what record(s) it failed.
>> I would run it multiple times until I find and eliminate ALL the records
>> of my file that it fails on.
>> When all bad records get eliminated and my file gets loaded correctly by
>> the current importer, I don't think I would have a problem sending you all
>> those bad records for you to analyze and see where the new importer has
>> gone bad.
>>
>> DO you think something like the above can be done?

At least it should - instead of "Failed" - say "Failed to read line nr %d".

That would reduce the burden of bisect.

~Frank

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: [GNC-dev] [GNC] Failed - import of QIF files from Quicken

2020-02-18 Thread Christopher Lam
Sorry. Please ask other devs on public mailing list.

On Tue, 18 Feb 2020 at 15:51, Tom Hatzigeorgiou  wrote:

> To do this someone will need to help me.
> I don't know how projects like this work.
> I have no idea where the program source exists and the tools I will need
> to manipulate it.
>
> I was thinking that a very simple way to debug the code is, for someone to
> place a display on a version of the new importer where every record that it
> processes gets displayed (in a log file) before it gets imported.
> This way by running the importer I will see at what record(s) it failed.
> I would run it multiple times until I find and eliminate ALL the records
> of my file that it fails on.
> When all bad records get eliminated and my file gets loaded correctly by
> the current importer, I don't think I would have a problem sending you all
> those bad records for you to analyze and see where the new importer has
> gone bad.
>
> DO you think something like the above can be done?
>
>
>
> --
> *From:* Christopher Lam 
> *Sent:* Tuesday, February 18, 2020 12:27 AM
> *To:* tomh...@hotmail.com ; gnucash-devel <
> gnucash-devel@gnucash.org>
> *Subject:* Fwd: [GNC] Failed - import of QIF files from Quicken
>
>
> That's fine. Maybe the other developers will be able to help. Feel free to
> download the sources to start debugging the qif importer.
>
> -- Forwarded message -
> From: *Tom Hatzigeorgiou* 
> Date: Tue, 18 Feb 2020, 1:20 pm
> Subject: Re: [GNC] Failed - import of QIF files from Quicken
> To: Christopher Lam 
>
>
> I understand that you want to recreate the problem so that you can fix it
> but this is my whole financial history and I wouldn't know where to start
> to anonymize it
> so I wouldn't be comfortable giving it away
>
> You should know that I am a programmer so I think I could follow
> instructions and could debug the importer for you to find out where it
> breaks at least with my data
> I would be wiling to do that because I like GNUCASH, I hate what Quicken
> is doing to long time users (like me), and I would keep control of my data.
>
>
>
> --
> *From:* Christopher Lam 
> *Sent:* Monday, February 17, 2020 5:55 PM
> *To:* Tom Hatzigeorgiou 
> *Cc:* gnucash-u...@gnucash.org 
> *Subject:* Re: [GNC] Failed - import of QIF files from Quicken
>
> Hello
> If you'll be kind to offer the QIF file in bugzilla or privately -- feel
> free to amend it manually first to anonymize details, it will be useful to
> debug.
> C
>
>
> On Mon, 17 Feb 2020 at 15:09, Tom Hatzigeorgiou 
> wrote:
>
> I have seen  few emails on this subject.
>
> Please see if the below statements would help you.
>
>
> I've been having a problem with importing my data from Quicken and into
> GNUCASH for Windows using a QIF file created by Quicken. I’ve over 30 years
> of data with thousands of transactions spanning multiple accounts and
> categories.
>
> I have found that there is an issue with the importer starting with
> version 3.2 (I think).
>
> As mentioned  by others, the importer would fail without giving an error.
>
> I have solved the issue by installing GNUCASH 3.1 importing my data and
> then installing the latest version (currently 3.8). Of course this assumes
> that you will be able to find the 3.1 install file. I hope you can find it
> in one of the archives.
>
> I don’t see any problem with my data after I open the file (in GNU 3.8)
> created by the GNUCASH 3.1.
>
> I was wondering if the developers could replace the importer (of the
> latest version) with the version that existed in the 3.1 version (until the
> import issue is fixed). I believe it would solved a lot of problems for a
> lot of people.
>
> I have another issue getting security prices and bank transaction. I have
> read a lot of solutions but none has help me. When I find a simple solution
> to this problem I will post here.
>
>
> ___
> gnucash-user mailing list
> gnucash-u...@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel