-
Notifications
You must be signed in to change notification settings - Fork 101
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
Legacy contract class corrupted when deserialized through ContractArtifact
#392
Comments
Looks like the switch to |
Adds test cases that asserts contract artifacts are not corrupted whether deserialized directly or via the `ContractArtifact` enum. The test for `LegacyContractClass` - `test_legacy_artifact_deser_from_contract_artifact` - is ignored due to a known issue #392.
Added a test case (that's disabled by default to avoid breaking CI) in #644, |
Adds test cases that asserts contract artifacts are not corrupted whether deserialized directly or via the `ContractArtifact` enum. The test for `LegacyContractClass` - `test_legacy_artifact_deser_from_contract_artifact` - is ignored due to a known issue #392.
Adds test cases that asserts contract artifacts are not corrupted whether deserialized directly or via the `ContractArtifact` enum. The test for `LegacyContractClass` - `test_legacy_artifact_deser_from_contract_artifact` - is ignored due to a known issue #392.
Due to a scientific notation issue, certain legacy (Cairo 0) contract artifacts can be different when deserializing directly and through the
ConrtractArtifact
enum. This leads to class hash errors, and hence failures on contract declaration.Details to be updated later. Creating this issue first so that it can be referenced from
starkli
.The text was updated successfully, but these errors were encountered: