You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
When called the function should return immediately if there is no back-pressure. When pre-checking is finished, the response is sent through result_tx.
PrecheckResult indicates on of the following outcomes:
succeeded - meaning we are pretty sure that compilation of the given PVF finishes producing a compiled artifact within the certain memory and time limits.
failed - we are pretty sure that compilation exceeds the certain memory and time limits.
internal error - this potentially can be returned if there are problems claiming a worker process to do the pre-checking job, or other spurious failures.
The execution happens on the validation host async task. When executed, it will check if the given PVF already compiled. If it is, then it will respond immediately.
The compilation should be performed with turned off parallel compilation. See paritytech/substrate#9605 details.
If the PVF is being compiled right now then we should kill the current process or wait until it finishes on its own. Then the process should be restarted under the required conditions. The actual compilation should not differ from what we currently have, with the exception of custom settings. As an alternative, we may want to compile any PVFs in such a mode that ensures the least variance at all times.
The text was updated successfully, but these errors were encountered:
Add a function into the validation host that will provide a way to pre-check a given wasm binary. (See #3211 for details on what pre-checking is).
The shape of the function would be:
When called the function should return immediately if there is no back-pressure. When pre-checking is finished, the response is sent through
result_tx
.PrecheckResult
indicates on of the following outcomes:The execution happens on the validation host async task. When executed, it will check if the given PVF already compiled. If it is, then it will respond immediately.
The compilation should be performed with turned off parallel compilation. See paritytech/substrate#9605 details.
If the PVF is being compiled right now then we should kill the current process or wait until it finishes on its own. Then the process should be restarted under the required conditions. The actual compilation should not differ from what we currently have, with the exception of custom settings. As an alternative, we may want to compile any PVFs in such a mode that ensures the least variance at all times.
The text was updated successfully, but these errors were encountered: