1.32: import --catchup no longer writes .latest files #2156
Labels
A-BUG
Something wrong, confusing or sub-standard in the software, docs, or user experience.
bounty
Thar's some kind o' loot on offer..
csv
The csv file format, csv output format, or generally CSV-related.
impact3
Affects just a few users.
regression
A backwards step, indicating a weakness in our QA. We don't like these.
severity4
Major usability/doc bug, crash, or any regression.
When I attempt to import a
CSV
from my bank and I specify the--catchup
option, the command runs successfully, however, the.latest.sample.csv
state file is not written. The existence of the file and it's content do not seem to have an impact on whether the command updates/creates the file.I've been able to reproduce this issue reliably on versions above
1.31
. The issue seems to have been introduced in1.32
and I think it may be a regression as I couldn't find anything in the release notes suggesting it was an intentional change.Please let me know if you need anything else to reproduce or if this is a problem on my end. Thanks!
Steps To Reproduce
Note, the commands assume you have the
LEDGER_FILE
environmental variable specified.>=1.32
CSV
that contains valid transactions for importinghledger import --catchup sample.csv
.latest.sample.csv
to see if it was created or updatedno new transactions found in CSV
Expected Result
The command finishes successfully, prints the number of transactions skipped, and updated the
.latest.sample.csv
file with the latest dates.Notes
When I run the
import
command without--catchup
, the journal file is updated and the.latest.sample.csv
file is created/updated correctly. The--catchup
option works for me in version1.31
so I'll continue using that for now.The text was updated successfully, but these errors were encountered: