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

CN: Assert max tuple size #787

Merged
merged 1 commit into from
Dec 23, 2024
Merged

Conversation

dc-mak
Copy link
Contributor

@dc-mak dc-mak commented Dec 23, 2024

In the buddy allocator, tuples can end up being larger than 8, and so the error comes up as a solver rather than a more helpful arity one. This commit inserts a quick fix to make it fail at a better location. It does not come with a test because the buddy allocator is too large and slow to cut down, and I don't know how to coax Cerberus into generating tuples that big.

In the buddy allocator, tuples can end up being larger than 8, and so
the error comes up as a solver rather than a more helpful arity one.
This commit inserts a quick fix to make it fail at a better location. It
does not come with a test because the buddy allocator is too large and
slow to cut down, and I don't know how to coax Cerberus into generating
tuples that big.
@dc-mak dc-mak merged commit 0ab06e0 into rems-project:master Dec 23, 2024
4 checks passed
@dc-mak dc-mak deleted the assert-tuple-max branch December 23, 2024 09:30
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.

1 participant