[GNC] Fwd: Price Source "Last up through Report Date" issue

[Gal Bar Mashiah]

This seems like a regression in 4.12.

Please see the bug report I opened:

https://bugs.gnucash.org/show_bug.cgi?id=798625

On Mon, Sep 26, 2022 at 11:35 PM Geoff <cleanoutmyshed at gmail.com
<https://lists.gnucash.org/mailman/listinfo/gnucash-user>> wrote:

>* Hi David
*>>* This is a longshot: I noticed that records in the Prices table have a
*>* timestamp, see attached screenshot.
*>>* So, perhaps, you ran the report for the 31st in the morning and the
*>* prices had an afternoon timestamp?
*>>* You could inspect your Prices and run the report at different times of
*>* the day to test this conjecture.
*>>* Regards
*>>* Geoff
*>* =====
*>>* On 27/09/2022 2:17 pm, David Carlson wrote:
*>* > This is odd.  While prices that were picked by GnuCash for the Tuesday,
*>* May
*>* > 31 dated account balance sheet report were actually the last prices in
*>* the
*>* > data before May 31, possibly several days earlier when there were prices
*>* > for every security actually dated May 31, the report which I created
*>* later
*>* > for Thursday June 30 picked the prices actually dated June 30.  There
*>* were
*>* > also prices dated June 29 and July 1 in the data for most or all the
*>* > securities in the report. Why is May 31 an outlier?
*>* >
*>* > ---------- Forwarded message ---------
*>* > From: David Carlson <david.carlson.417 at gmail.com
<https://lists.gnucash.org/mailman/listinfo/gnucash-user>>
*>* > Date: Mon, Sep 26, 2022 at 4:15 PM
*>* > Subject: Price Source "Last up through Report Date" issue
*>* > To: gnucash-user at gnucash.org
<https://lists.gnucash.org/mailman/listinfo/gnucash-user>
<gnucash-user at gnucash.org
<https://lists.gnucash.org/mailman/listinfo/gnucash-user>>
*>* >
*>* >
*>* > I finally had a real test for this price source while running an account
*>* > report for May 31, 2022 in release 4.8, which I only recently adopted.
*>* > Unfortunately, it took prices from May 30 for this report, which is not
*>* > exactly as described by the title.  Has this been corrected since release
*>* > 4.8?
*>* >
*


-- 
David Carlson