Nice to hear that it's fixable. The pricedb entries have unreasonable precision and was fixed a few months ago, but existing entries remain. This is still a worthwhile bug to fix.
On Sun, 28 Jun 2020 at 14:43, Lipp F. <flipp...@gmail.com> wrote: > Hi Christopher, > > Your suggestion about verifying pricedb was invaluable. I cannot thank you > enough. > > I was able to identify the security responsable by disabling sub-accounts, > one by one, until I was left with only the one generation the error. I have > checked pricedb for that specific security and I've noticed that prices > prior to Jul 9 are recorded fractional (as 273 + 342939880122/353546268167) > but displayed correctly (as 273.97). So, it was enough to edit the entry > and re-enter the correct decimal value and everything works fine. > > On Sat, Jun 27, 2020 at 11:37 PM Christopher Lam < > christopher....@gmail.com> wrote: > >> Hi Lipp >> The usual approach is to file a bug in bugs.gnucash.org >> Include the exact version used (3.10?) >> Also you are using pricedb - it would be worth reviewing the pricedb >> entries around 9th July and add this to the bug report. >> C >> >> On Sat, 27 Jun 2020 at 14:28, Lipp F. <flipp...@gmail.com> wrote: >> >>> Wondering if anyone can help. I am trying to run the "Net Worth >>> Linechart" >>> report only for brokerage accounts. It works fine form Jul 9, 2019 to >>> date >>> but any earlier date than Jul 9 throws the error. >>> >>> On Jul 9 I only have two monthly divident payments, recorded the same way >>> as ever. >>> >>> >>> Thanks. >>> >>> >>> Report error >>> > An error occurred while running the report. >>> > 19 (eval-string "(gnc:report-run 8)" #<undefined>) >>> > In ice-9/boot-9.scm: >>> > 2312:4 18 (save-module-excursion #<procedure 13576dc0 at ice-9/ev…>) >>> > In ice-9/eval-string.scm: >>> > 38:6 17 (read-and-eval #<input: string 134c5f50> #:lang _) >>> > In report.scm: >>> > 776:4 16 (gnc:report-run _) >>> > In c-interface.scm: >>> > 64:23 15 (gnc:backtrace-if-exception _ . _) >>> > 22:4 14 (gnc:call-with-error-handling _ _) >>> > In ice-9/boot-9.scm: >>> > 829:9 13 (catch #t #<procedure 134eb558 at c-interface.scm:23:6…> >>> …) >>> > In c-interface.scm: >>> > 26:40 12 (_) >>> > In report.scm: >>> > 780:24 11 (_) >>> > 756:25 10 (gnc:report-render-html #<<report> type: d8b63264186b1…> >>> …) >>> > In net-charts.scm: >>> > 326:30 9 (net-renderer #<<report> type: d8b63264186b11e19038001…> >>> …) >>> > 247:6 8 (process-datelist _ _ _) >>> > In commodity-utilities.scm: >>> > 927:17 7 (gnc:sum-collector-commodity #<procedure f7043e0 at re…> >>> …) >>> > In srfi/srfi-1.scm: >>> > 592:29 6 (map1 (#<<gnc-monetary> commodity: #<swig-pointer gn…> …)) >>> > 592:29 5 (map1 (#<<gnc-monetary> commodity: #<swig-pointer gn…> …)) >>> > 592:29 4 (map1 (#<<gnc-monetary> commodity: #<swig-pointer gn…> …)) >>> > 592:17 3 (map1 (#<<gnc-monetary> commodity: #<swig-pointer gn…> …)) >>> > In commodity-utilities.scm: >>> > 930:46 2 (_ #<<gnc-monetary> commodity: #<swig-pointer gnc_commo…>) >>> > 777:12 1 (gnc:exchange-by-pricedb-nearest _ #<swig-pointer gnc_…> >>> …) >>> > In unknown file: >>> > 0 (gnc-pricedb-convert-balance-nearest-price-t64 #<swig-…> >>> …) >>> > Throw to key `numerical-overflow' with args `("/" "Numerical overflow" >>> #f >>> > #f)'. >>> _______________________________________________ >>> 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. >>> >> _______________________________________________ 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.