-
Notifications
You must be signed in to change notification settings - Fork 3
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
CodeRejected: module imports a non-existent function #243
Comments
|
@yjhmelody did you get a chance to take a look at the fix (or the one suggested in this issue ). |
@yjhmelody
I believe it should be top priority as without fixing this ask! is essentially broken for all major parachains. |
Ok, will be updated |
That's not true. You should config it such as: {
"targets": {
"debug": {
"sourceMap": true,
"debug": true
},
"release": {
"sourceMap": false,
"optimizeLevel": 3,
"shrinkLevel": 2,
"converge": false,
"noAssert": false
}
},
"options": {
"transform": ["ask-transform", "as-serde-transform"],
"importMemory": true,
"initialMemory": 2,
"maximumMemory": 16,
"noExportMemory": true,
"runtime": "stub",
"use": "abort=",
"disable": ["Sign-extension"]
}
} or inherent this config: "extends": "ask-lang/asconfig.json", I did not see |
Oh, I misunderstood, indeed, I need to study further |
Related issues about |
Problem: -
Error while deploying contracts that contains methods that deletes storage states. That includes operation like
Mapping.delete()
that callenv().clearContractStroage()
.Temporary Fix: -
Commented out the new
seal_clear_storage
from__unstable__.ts
, that overshadows the oldseal_clear_storage
fromseal0.ts
ask/as-packages/as-contract-runtime/assembly/unstable.ts
Lines 34 to 35 in a1bd060
Substrate Contracts Node Log
v0.22
v0.23
Steps to reproduce: -
Build and deploy any contract that has
delete()
method. Below is the minimal reproduction contract.Notes (Not related to this issue) :-
Cannot deploy any contract build with
ark-lang
v0.4.0 on latestsubstrate-contracts-node
v0.23.Always fails with below error.
Maybe related to paritytech/substrate#207
The text was updated successfully, but these errors were encountered: