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

fix: parsing large labels over int32.MaxValue caused a loop in the parser #497

Merged
merged 1 commit into from
Mar 3, 2023

Conversation

martin1cerny
Copy link
Member

Toolkit currently reads entity labels as integers. This is for performance reasons as keeping all entity labels as long would increase amount of memory used by the applications considerably. Also, Int32.MaxValue provides enough space even for very large models. In the future, we may introduce internal parser time mapping to handle these special files.

In the current implementation, exception in label conversion caused a loop. This was only broken by maximum number of errors, but that is a week constraint and reported wrong number of issues. This fix doesn't introduce support for long labels.

…rser

This was only broken by maximum number of errors, but that is a week constraint and
reported wrong number of issues. **This fix doesn't introduce support for long labels.**
@martin1cerny martin1cerny merged commit 896ccad into develop Mar 3, 2023
@martin1cerny martin1cerny added the bug Confirmed bug label Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bug
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

1 participant