Issue #169: Consider always creating some transaction object even when there are errors. (blais/beancount)
9 views
Skip to first unread message
Martin Blais
Jun 15, 2017, 11:34:30 PM6/15/17
to bean...@googlegroups.com
New issue 169: Consider always creating some transaction object even when there are errors.
https://bitbucket.org/blais/beancount/issues/169/consider-always-creating-some-transaction
Martin Blais:
> Furthermore, attempting to debug with bean-doctor doesn't quite work for me. The transaction in question starts at line 17. But beandoctor context <filename> 17 returns the context for the previous transaction at line 13.
That's interesting; if there's no error, it works fine.
However, I think in this case, because this error was irrecoverable, the transaction was skipped, and the behavior of the line-number selection is to select the closest previous transaction. It does result in an odd behavior.
Maybe I should always create transactions even when there are errors.
This would require a fair amount of testing.
It's not necessarily a bad idea.
Responsible: blais
https://bitbucket.org/blais/beancount/issues/169/consider-always-creating-some-transaction
Martin Blais:
> Furthermore, attempting to debug with bean-doctor doesn't quite work for me. The transaction in question starts at line 17. But beandoctor context <filename> 17 returns the context for the previous transaction at line 13.
That's interesting; if there's no error, it works fine.
However, I think in this case, because this error was irrecoverable, the transaction was skipped, and the behavior of the line-number selection is to select the closest previous transaction. It does result in an odd behavior.
Maybe I should always create transactions even when there are errors.
This would require a fair amount of testing.
It's not necessarily a bad idea.
Responsible: blais
Reply all
Reply to author
Forward
0 new messages