Skip to content
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

Bug in optimize #173

Open
emricksinisonos opened this issue Mar 9, 2022 · 0 comments
Open

Bug in optimize #173

emricksinisonos opened this issue Mar 9, 2022 · 0 comments

Comments

@emricksinisonos
Copy link
Collaborator

I have an issue when I run the optimize algorithm on this FST.

The algorithm panics because of an unwrap() occurring in the decode function that happens just after a minimize. More exactly, decode(tr.ilabel) is called with an ilabel == 0 which implies calling a get on a negative value here.

The issue seems to be introduced by this PR #166 as the algorithm doesn't panic in the latest commit before that change (8f7f486).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant