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 <tomh...@hotmail.com> 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-user mailing list
gnucash-user@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.
