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

Make --blocks-per-json-file unsigned #46

Merged
merged 1 commit into from
Feb 23, 2024
Merged

Conversation

boomanaiden154
Copy link
Collaborator

Before this patch, --blocks-per-json-file was setup as unsigned in the flag definitions, but the value was assigned to a normal int later on. This resulted in the check that the value is <= triggering with the default value of the maximum unsigned 32 bit integer. This patch fixes that by assigning the value of the flag to an unsigned value rather than a normal int.

Before this patch, --blocks-per-json-file was setup as unsigned in the
flag definitions, but the value was assigned to a normal int later on.
This resulted in the check that the value is <= triggering with the
default value of the maximum unsigned 32 bit integer. This patch fixes
that by assigning the value of the flag to an unsigned value rather than
a normal int.
@ondrasej ondrasej merged commit e07db25 into main Feb 23, 2024
8 checks passed
@boomanaiden154 boomanaiden154 deleted the blocks-per-json-file-unsigned branch February 24, 2024 00:23
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

Successfully merging this pull request may close these issues.

2 participants