That is quite interesting.

As noted, I don't have any >6 level Asset (or Liability) accounts. But I do have level-7 Expense accounts. I tried the Expense Chart & Expense Pie Charts, and both execute without errors for both All and '6' options. (and yes, those level-7 accounts have many transactions in them)

Now, this could still be an OS specific thing, but if those two work for you, perhaps Chris could merge the code from them to the other offending charts/reports.

I see he made a change to not report deeper than '6' but I haven't received clarification if that is just for the option '6' or for 'All' as well. (which would render reporting/charting deeper than level-6 impossible.)

I'll see about creating some dummy level-7 asset accounts and try to trigger the error.

Regards,
Adrien

On 12/7/20 11:05 AM, D. via gnucash-user wrote:
Further to this: you asked whether the problem occurs with level All. 
Interestingly, this option does result in the error occurring again.

However, when All is selected, the default report triggers the error with a 
different option number and a different number of iterations. This time, the 
erroneous value is indicated as '11', and it only occurs once. When 6 is 
selected, increasing the number of slices changes the number of times the error 
is iterated, although there isn't an apparent correlation between the slices 
shown and the number of errors. In other words, when I increase the number of 
slices by one (from the default 8 to 9), the added slice in the display is not 
at the seventh level, but the error is now repeated twice. The iterations do 
not change with the All setting; they remain at 1 regardless of the number of 
slices.

I've looked at this more extensively now. I tried other "Slice-based" reports, 
under the assumption that their logic would cause similar results. I include my observed 
results below. I list the setting, followed by the error iteration in parentheses when 
the default settings are used, with only the depth value changed. In all cases, the All 
error was for option 11, and the 6 error was for option 7.

Asset Chart (resulting tab is titled "Assets Over Time"): All (1)   6 (6)
Asset Piechart (resulting tab is titled "Assets"): All (0)   6 (5)
Liability Chart (resulting tab is titled "Liabilities Over Time"): All (1)    6 
(2)
Liability Piechart (resulting tab is titled "Liabilities"): All (1)  6 (2)

It is interesting that the Asset Piechart didn't trigger any errors with the 
All setting. That was the only clean version.

I will note that when I initially ran the Liability reports, I received no 
errors. This was because I didn't have any liabilities accounts at level 7. To 
verify this, I added dummy levels to one of the liabilities to reach level 7, 
and the errors started up. Further, I am confident that the number of 
iterations for the error is directly related to the number of level 6 accounts 
with level 7 children. When I add a parallel set of dummy accounts down to 
level 7 on another branch in Liabilities, the error iteration goes up by one.

The mere presence of the level 7 account triggers errors. It didn't matter 
whether the dummy accounts had transactions in them, or whether the account was 
displayed in the resulting report. However, if the level 7 accounts are all 
empty, the error only triggers once. Adding a transaction to one of the dummy 
accounts increases the iteration to two, and adding to the other dummy also 
increases the iteration.  This suggests that there is some relation between the 
number of seventh level slices to be displayed (as opposed to simply existing), 
but a base problem with that level on principle.

_______________________________________________
gnucash-user mailing list
[email protected]
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.

Reply via email to