If what I asked cannot be done i will try to produce a file with the errorsome other way I would suggest to take these emails offline. I think they confuse the user community
I will be in touch Thanks On Feb 18, 2020 5:34 PM, "Frank H. Ellenberger" <frank.h.ellenber...@gmail.com> wrote: 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-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
