[GNC] Currency Database empty

[John Ralls]

The only reason to not CC the list is if you're specifically invited to send confidential data to a developer.

You're right, it's bug 797046. I'd mistaken that for Windows only this morning when looking over the bug reports, but Mike Alexander had seen it on MacOS too. As you probably surmised it's fixed in git. Unfortunately there aren't any MacOS nightlies for you to try so your best bet is to use GnuCash 3.3 until 3.5 comes out.

Regards,
John Ralls



> On Feb 16, 2019, at 3:20 PM, Keith Bellairs <keith at bellairs.org> wrote:
> 
> John,
> 
> As you might expect, fixing the broken date  allowed gnc to start without adding warnings to the trace file. Thanks for the pointer.
> 
> The currency error in the price db is still there - currency exchange rates do not display and cannot be added (or maybe are added and do not display). I ran gnc with --debug, but the 23M file is a little unwieldy.
> 
> Related to the https://bugs.gnucash.org/show_bug.cgi?id=797046 bug? I am using MacOS.
> 
> I stopped cc to the Gnucash users while this works out.
> 
> Keith
> 
> On Sat, Feb 16, 2019 at 3:11 PM John Ralls <jralls at ceridwen.us> wrote:
> Seems you've got a bad date in your price database and it's messed up the in-memory pricedb. Make a copy of your data file, decompress it if necessary, and open it in a text editor. search for "201-12-11" and correct it. Be sure to save as plain text if you're using TextEdit. Open the saved file in GnuCash and see if that's fixed it.
> 
> Regards,
> John Ralls
> 
> > On Feb 16, 2019, at 8:40 AM, Keith Bellairs <keith at bellairs.org> wrote:
> > 
> > John,
> > 
> > xml backend.
> > 
> > not running with -debug but trace has some of these:
> > * 10:50:08  WARN <qof.engine> [gnc_dmy2time64_internal()] Date computation error from Y-M-D 201-12-11: Year is out of valid range: 1400..9999
> > * 10:56:13  CRIT <gnc.backend.xml> xmlNodePtr time64_to_dom_tree(const char *, const time64): assertion 'time != INT64_MAX' failed
> > * 10:56:13  CRIT <gnc.backend.xml> xmlNodePtr time64_to_dom_tree(const char *, const time64): assertion 'time != INT64_MAX' failed
> > 
> > But the date error does not seem to be coming from the Price Database tool. (Restarted gnc, went to price tool, tired to add currency exchange, failed - but no CRIT trace. The WARN appeared when gnc was started and before using price tool.)
> > 
> > Keith
> > 
> > 
> > 
> > On Sat, Feb 16, 2019 at 11:25 AM John Ralls <jralls at ceridwen.us> wrote:
> > 
> > 
> > > On Feb 16, 2019, at 8:02 AM, Keith Bellairs <keith at bellairs.org> wrote:
> > > 
> > > Version: 3.4
> > > Build ID: 3.4+ (2018-12-30)
> > > Finance::Quote: 1.47
> > > MacOS 10.14.3 (recent update)
> > > 
> > > Recently moved up from gnc 2 to 3.4. Opened Price Database tool and ran get
> > > quotes, as I have done for years. Got the alert box that it couldn't get
> > > CAD. That's not a surprise. Update to prices was completed and I went to
> > > hand enter a new CAD/USD price. No CAD or USD price history shows (there
> > > should have been 15 years worth). So I selected ADD to at least have the
> > > current exchange rate. After clicking Apply and / or OK, no exchange rate
> > > was added and the set of exchange rates is still empty.
> > > 
> > > Is this known? Is there a fix?
> > 
> > I thought that I'd seen something similar from last month but I can't find it. What backend are you using? Are there any useful messages in the trace file [1]?
> > 
> > Regards,
> > John Ralls
> > 
> > [1] https://wiki.gnucash.org/wiki/Tracefile
> > 
>