Unbalanced multi-commodity transaction after upgrading to `1.32.1`

[stewmehr]

Hi there,

I have trouble with a slightly modified/updated version of the transaction mentioned in #2057. The following ledger file

commodity 1,000.00 €
commodity 1,000.0000 "LYX0Q0"

2023-01-18=2023-01-16
     assets:stewmehr:bnp:giro                                       -304.0 €
     assets:stewmehr:bnp:depot:LYX0Q0:20230116    1.5111 "LYX0Q0" @ 200.65 €
     expenses:depot:gebuehren                                         0.80 €

used to cause no issues on my end until I recently upgraded hledger. It appears that the significant digits that are defined along with the commodities are no longer respected. I am well aware that the transaction is not balanced in a strict sense (there should be a difference of -0,002215 €) but as far as I can remember previous versions of hledger were able to "ignore" this numerical issue.

13 | 2023-01-18=2023-01-16
   |     assets:stewmehr:bnp:giro                                       -304.0 €
   |     assets:stewmehr:bnp:depot:LYX0Q0:20230116    1.5111 "LYX0Q0" @ 200.65 €
   |     expenses:depot:gebuehren                                         0.80 €

This multi-commodity transaction is unbalanced.
The real postings' sum should be 0 but is: 0
Consider adjusting this entry's amounts, adding missing postings,
or recording conversion price(s) with @, @@ or equity postings.
This multi-commodity transaction is unbalanced.
The real postings' sum should be 0 but is: 0
Consider adjusting this entry's amounts, adding missing postings,
or recording conversion price(s) with @, @@ or equity postings.

Version:
hledger 1.32.1, mac-x86_64

[simonmichael]

The example above gives me a different error, because of the inconsistent decimal marks - could you update it ?

The real postings' sum should be 0 but is: 303199255 € 

[stewmehr]

Oh no, I am sorry. Serves me right for manually adding the two lines at the top from memory instead of copying them from my journal files. I have updated the example.

[simonmichael]

Can't reproduce yet.

[simonmichael]

Hi @stewmehr, did you resolve this ? The current example above does not raise an error for me with 1.32.1 or other versions.

[stewmehr]

Hi @simonmichael,
sorry for not following up on this - I simply downgraded to a previous version of hledger and completely forgot about this minor annoyance. Will try and investigate this further on my end this week.

[simonmichael]

Closing, let me know if it shows up again.