unknown import: `ethereum::ethereum.call` has not been defined

[leoyvens]

Summary

This happens when a file data source handler uses contract calls directly or is in the same AssemblyScript file as other handlers which use contract calls. If the contract call is done by a different handler in the same file, this can be fixed by putting the file data source handler in its own file, which is best practice.

Potential Fix

Contract calls in file data source handlers could be enabled by somehow passing the ethereum.call host fn when instantiating an offchain data source, relevant code:

graph-node/runtime/wasm/src/host.rs

Lines 137 to 141 in 92670f2

	let host_fns = data_source
	.as_onchain()
	.map(|ds| runtime_adapter.host_fns(ds))
	.transpose()?
	.unwrap_or_default();

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.

[azf20]

This is still relevant - @leoyvens does this fail at build-time or at runtime?

[PierreJeanjacquot]

From my experience, it fails at runtime.

I'm currently interested in the issue because I've a use case with off-chain data that is referenced on-chain by an IPFS CID and that content must be verified on-chain.

I got an on-chain handler that parses an on-chain CID and triggers the creation of a DataSourceTemplate based on the IPFS document.
In the off-chain file handler I would like to check some on-chain properties by binding a contract (address passed through context), which leads to the error

ERRO Subgraph failed with non-deterministic error: failed to process trigger: module instantiation failed: unknown import: `ethereum::ethereum.call` has not been defined

I'm not sure if what I want to achieve is possible or if I'm doing something wrong