search

Lay3rLabs / avs-toolkit

MIT License
6 stars 3 forks source link

Error: cannot find task.id #103

Open ethanfrey opened 3 hours ago

ethanfrey commented 3 hours ago

After going through the DEMO.md, with latest version of the layer-sdk and wasmatic and avs-toolkit, everything works until the end.

cargo run -- --target=local task-queue add-task -b '{"x": 12}' -d 'test 1'

Returns:

Error: couldn't find event attribute for wasm.task_id

But the event is added to the task queue (marked open). The wasmatic instance also doesn't pick it up. docker logs -f localnode-wasmatic-1 says:

2024-10-21T08:10:22.019445Z ERROR tokio_cron_scheduler::job::creator: Error running job ec71e499-4a80-4a27-8cc6-5568162e643a RecvError(())
thread 'tokio-runtime-worker' panicked at /myapp/src/operator.rs:240:81:
called `Result::unwrap()` on an `Err` value: SerdeJson(Error("invalid type: string \"300000000000\", expected u64", line: 1, column: 99))
ethanfrey commented 3 hours ago

The wasmatic part was fixed here: https://github.com/Lay3rLabs/wasmatic/pull/55

Still need to fix the cli command