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

Exception : Value was either too large or too small for an unsigned byte. #57

Open
amuljk opened this issue Feb 26, 2019 · 2 comments
Open

Comments

@amuljk
Copy link

amuljk commented Feb 26, 2019

FleeTest.zip

Hi,

Attached is a zip file that contains a simple .NET Core console application. In it, there are 3 expressions that are executed using the latest .NET Core Flee library. All the 3 expressions fail with an exception "Value was either too large or too small for an unsigned byte."

Note that the expressions are similar with minor variations.

Seems like the issue is while determining a long branch.

@amuljk
Copy link
Author

amuljk commented Jan 5, 2021

Any updates on this issue?

@hunkydoryrepair
Copy link
Contributor

I believe this is the same as bug #86 that was recently entered. I resolved it on my fork and issued a pull request. The pull request shows the changes you'd need to make if they don't get incorporated.

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

2 participants