Loses precision on amounts!

[tbm]

b2l turns 10.2253 units into 10.22 units, which means the file no longer balances.

It seems the precision is influenced by other transactions. If the transaction is followed by 2 or more with lower precision, that precision is adopted. If there's only 1 other transaction, it's not lost.

2022-12-21 * "Investment"
    Assets:Investments  10.2253 GB00B80QFW04 {2.984917082 GBP}
    Assets:Investments

2022-12-21 * "Investment"
    Assets:Investments   1.12 GB00B80QFW04 {2.984917082 GBP}
    Assets:Investments

2022-12-21 * "Investment"
    Assets:Investments   2.23 GB00B80QFW04 {2.984917082 GBP}
    Assets:Investments

Output:

2022-12-21 * Investment
    Assets:Investments               10.23 "GB00B80QFW04" {2.984917082 GBP}
    Assets:Investments
...

[tbm]

bean-report print has the right info but I see that bean-query doesn't seem to, so maybe this is a beancount issue. I need to invest another day.

[tbm]

b2l turns 10.2253 units into 10.22 units, which means the file no longer balances.

My original test case (when converted to ledger) no longer balances. It seems ok in beancount. I need to investigate.

[zacchiro]

I'm seeing this too, where amounts with 2 digits (e.g., -200.95) are truncated and rounded to 0 digits (e.g., ``-201). This is pretty bad… It also seems to be non-deterministics somehow, but I couldn't figure out yet what's the trigger. It feels like it's more likely to happen if there are many transactions in the input beancount file than if there are very few.