Skip to content

Conversation

@jacinta-stacks
Copy link
Contributor

@jacinta-stacks jacinta-stacks commented Nov 14, 2025

When writing clarity RuntimeError tests, I saw this. Fixed error message and also removed the use of VmExecutionError(RuntimeError). This error is not really meant to be used for input parsing/config parsing errors which is what it basically is in clarity-cli. Changed it to be just a string. Makes life easier for me and I think its actually more correct. Happy for push back on this though.

Signed-off-by: Jacinta Ferrant <jacinta@stackslabs.com>
… a VmExecutionError when parsing an input string

Signed-off-by: Jacinta Ferrant <jacinta@stackslabs.com>
Copy link
Contributor

@federico-stacks federico-stacks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sense! IMHO basic types shouldn't be aware of the clarity errors. They should be emitted based on the usage instead.

Copy link

@francesco-stacks francesco-stacks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

Copy link
Contributor

@brice-stacks brice-stacks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems fine to me if no users of this complain about the error type (as evidenced by a lack of compile-time errors).

@jacinta-stacks jacinta-stacks added this pull request to the merge queue Nov 17, 2025
Merged via the queue into stacks-network:develop with commit 46d7bd1 Nov 17, 2025
308 of 312 checks passed
@jacinta-stacks jacinta-stacks deleted the chore/fix-clarity-error-string branch November 17, 2025 19:09
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.

4 participants