Bug report:Resource table mismatch caused by mixing resource handle index and handle value.

[xiaozzzZZzzz240]

cplusplus.zip
generated_wit_00000.wit.zip
generated_wit_00000b.wit.zip
python.zip
world0-pvwxtgtmlk_fromPython.wasm.zip
world1-consumer_fromC++_importworld0-pvwxtgtmlk_fromPython.wasm.zip
world1-consumer_fromC++.wasm.zip

Summary

Maybe realted to #1381.
Resource table mismatch caused by mixing resource handle index and handle value.

Environment

jco 1.16.1
wasmtime 41.0.0
OS: macOS Sequoia 15.7
CPU: Intel Core i7

Reproduce steps

The specific reproduction steps are as follows:

1. Use the following command to generate Python binding files from generated_wit_00000.wit.
   componentize-py -d xxx/witfiles/package3hl16smu1p -w world0-pvwxtgtmlk bindings xxx/python/world0-pvwxtgtmlk

2. Implement the Python program as shown in python.zip.

3. Use the following command to generate Wasm component file from Python.
   cd xxx/python/world0-pvwxtgtmlk
componentize-py --wit-path xxx/witfiles/package3hl16smu1p --world world0-pvwxtgtmlk componentize world0-pvwxtgtmlk_generated -o xxx/componentfiles/world0-pvwxtgtmlk_fromPython.wasm

4. Use the following command to generate C++ binding files from generated_wit_00000b.wit.
   wit-bindgen cpp xxx/witfiles/package3hl16smu1p --world world1-consumer --out-dir xxx/cplusplus/world1-consumer

5. Implement the C++ program as shown in cplusplus.zip.

6. Use the following command to generate Wasm component file from C++.
   xxx/WASI/wasi-sdk-27.0/wasi-sdk-27.0-x86_64-macos/bin/wasm32-wasip2-clang++ -std=c++23 -o xxx/componentfiles/world1-consumer_fromC++.wasm -mexec-model=reactor xxx/cplusplus/world1-consumer/world1-consumer_generated.cpp xxx/cplusplus/world1-consumer/world1_consumer.cpp xxx/cplusplus/world1-consumer/world1_consumer_component_type.o

7. Use wac to combine the two Wasm component files:
   wac plug xxx/componentfiles/world1-consumer_fromC++.wasm --plug xxx/componentfiles/world0-pvwxtgtmlk_fromPython.wasm -o xxx/componentfiles/world1-consumer_fromC++_importworld0-pvwxtgtmlk_fromPython.wasm

8. Use wasmtime to run the final Wasm component file:
   wasmtime run world1-consumer_fromC++_importworld0-pvwxtgtmlk_fromPython.wasm
   Wasmtime prints:

[min-group] begin
[dbg] py:make_file id=1
[dbg] py:file.__init__ path=mem://id-1 id=1
[dbg] py:make_file id=2
[dbg] py:file.__init__ path=mem://id-2 id=2
[dbg] py:make_group
[dbg] py:group.__init__
[dbg] py:group.take_a
[min-group] after-take-a

9. Use jco to run the same final Wasm component file:
   jco run world1-consumer_fromC++_importworld0-pvwxtgtmlk_fromPython.wasm
   jco prints:

[min-group] begin
[dbg] py:make_file id=1
[dbg] py:file.__init__ path=mem://id-1 id=1
[dbg] py:make_file id=2
[dbg] py:file.__init__ path=mem://id-2 id=2
[dbg] py:make_group
[dbg] py:group.__init__
AttributeError: '' object has no attribute 'take_a'

thread '<unnamed>' panicked at runtime/src/lib.rs:499:21:
Python function threw an unexpected exception
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
RuntimeError: unreachable
    at libc.so.abort (wasm://wasm/libc.so-001e65fe:wasm-function[458]:0x1041d)
    at wasm://wasm/02a772c2:wasm-function[306]:0xf8e8
    at libcomponentize_py_runtime.so.std::sys::pal::wasi::helpers::abort_internal::h118dde344a79086c (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2193]:0xceb72)
    at libcomponentize_py_runtime.so.std::process::abort::h2738589d00d7233e (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[1645]:0xb87f6)
    at libcomponentize_py_runtime.so.__rustc::__rust_abort (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2002]:0xc7330)
    at libcomponentize_py_runtime.so.__rustc::__rust_start_panic (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2208]:0xcfc4c)
    at libcomponentize_py_runtime.so.__rustc::rust_panic (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2035]:0xc8a1e)
    at libcomponentize_py_runtime.so.std::panicking::rust_panic_with_hook::h02d894de16d94192 (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2034]:0xc899c)
    at libcomponentize_py_runtime.so.std::panicking::begin_panic_handler::_$u7b$$u7b$closure$u7d$$u7d$::he125d401eefa4f33 (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[1573]:0xb451a)
    at libcomponentize_py_runtime.so.std::sys::backtrace::__rust_end_short_backtrace::h31a9416a2c4ea1cb (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[1572]:0xb4442)

Simplified reproduction steps

1. Use wasmtime to run the final Wasm component file:
   wasmtime run world1-consumer_fromC++_importworld0-pvwxtgtmlk_fromPython.wasm
   Wasmtime prints:

[min-group] begin
[dbg] py:make_file id=1
[dbg] py:file.__init__ path=mem://id-1 id=1
[dbg] py:make_file id=2
[dbg] py:file.__init__ path=mem://id-2 id=2
[dbg] py:make_group
[dbg] py:group.__init__
[dbg] py:group.take_a
[min-group] after-take-a

2. Use jco to run the same final Wasm component file:
   jco run world1-consumer_fromC++_importworld0-pvwxtgtmlk_fromPython.wasm
   jco prints:

[min-group] begin
[dbg] py:make_file id=1
[dbg] py:file.__init__ path=mem://id-1 id=1
[dbg] py:make_file id=2
[dbg] py:file.__init__ path=mem://id-2 id=2
[dbg] py:make_group
[dbg] py:group.__init__
AttributeError: '' object has no attribute 'take_a'

thread '<unnamed>' panicked at runtime/src/lib.rs:499:21:
Python function threw an unexpected exception
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
RuntimeError: unreachable
    at libc.so.abort (wasm://wasm/libc.so-001e65fe:wasm-function[458]:0x1041d)
    at wasm://wasm/02a772c2:wasm-function[306]:0xf8e8
    at libcomponentize_py_runtime.so.std::sys::pal::wasi::helpers::abort_internal::h118dde344a79086c (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2193]:0xceb72)
    at libcomponentize_py_runtime.so.std::process::abort::h2738589d00d7233e (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[1645]:0xb87f6)
    at libcomponentize_py_runtime.so.__rustc::__rust_abort (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2002]:0xc7330)
    at libcomponentize_py_runtime.so.__rustc::__rust_start_panic (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2208]:0xcfc4c)
    at libcomponentize_py_runtime.so.__rustc::rust_panic (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2035]:0xc8a1e)
    at libcomponentize_py_runtime.so.std::panicking::rust_panic_with_hook::h02d894de16d94192 (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[2034]:0xc899c)
    at libcomponentize_py_runtime.so.std::panicking::begin_panic_handler::_$u7b$$u7b$closure$u7d$$u7d$::he125d401eefa4f33 (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[1573]:0xb451a)
    at libcomponentize_py_runtime.so.std::sys::backtrace::__rust_end_short_backtrace::h31a9416a2c4ea1cb (wasm://wasm/libcomponentize_py_runtime.so-0052fcc2:wasm-function[1572]:0xb4442)

Result Analysis

The program logic is calling take-a, and the runtime should first use the handle to retrieve the Python Group object from the resource table, and then call its take_a method.
This maybe a bug about resource table mismatch caused by mixing resource handle index and handle value.

[vados-cosmonic]

Hello @xiaozzzZZzzz240 , please make a hosted reproduction repo available.

Also, if all the recent issue filed are related to resources use from python (and are reasonably in the same place), please combine the issues into one.

[xiaozzzZZzzz240]

Hello @xiaozzzZZzzz240 , please make a hosted reproduction repo available.

Also, if all the recent issue filed are related to resources use from python (and are reasonably in the same place), please combine the issues into one.

Thanks for your reply. All the files are in the repo : https://github.com/xiaozzzZZzzz240/jco_issue_1384