New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forecasting bug in hledger 1.10 #852

Closed
peti opened this Issue Jul 29, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@peti
Contributor

peti commented Jul 29, 2018

When I attempt to process the following file

~ every 31st March
    Bank             EUR 1
    Mortgage

with hledger print --forecast, the tool crashes, saying:

hledger: Prelude.!!: negative index

The same command worked fine with previous versions.

@peti

This comment has been minimized.

Show comment
Hide comment
@peti

peti Jul 29, 2018

Contributor

Other period transactions still work fine, so I reckon that the issue is with that particular period expression.

Contributor

peti commented Jul 29, 2018

Other period transactions still work fine, so I reckon that the issue is with that particular period expression.

@cnicolai

This comment has been minimized.

Show comment
Hide comment
@cnicolai

cnicolai Jul 30, 2018

Contributor

This could be related to #847 since lowercasing "March" seems to solve it.

Contributor

cnicolai commented Jul 30, 2018

This could be related to #847 since lowercasing "March" seems to solve it.

@simonmichael

This comment has been minimized.

Show comment
Hide comment
@simonmichael

simonmichael Jul 30, 2018

Owner

Thanks for the report! This was a regression in hledger 1.10.

Owner

simonmichael commented Jul 30, 2018

Thanks for the report! This was a regression in hledger 1.10.

@peti

This comment has been minimized.

Show comment
Hide comment
@peti

peti Jul 30, 2018

Contributor
Contributor

peti commented Jul 30, 2018

@simonmichael simonmichael changed the title from Forecasting bug in hledger 0.10 to Forecasting bug in hledger 1.10 Jul 30, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment