eye-gu commented on code in PR #6356:
URL: https://github.com/apache/shenyu/pull/6356#discussion_r3373487599


##########
shenyu-plugin/shenyu-plugin-wasm-api/src/test/go-wasm-plugin/Makefile:
##########
@@ -0,0 +1,34 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+
+WASM_FILE := 
org.apache.shenyu.plugin.wasm.api.AbstractWasmPluginTest\$$GoWasmPlugin.wasm
+RESOURCES_DIR := ../resources
+
+.PHONY: build clean
+
+build:
+       @echo "Building Go WASM plugin..."
+       tinygo build -target wasm-unknown -opt=2 -no-debug -panic=trap -o 
plugin.wasm main.go

Review Comment:
   This is an inherent limitation of pure-Java WASM runtimes: proc_exit in WASI 
command modules terminates execution via a Java exception, which unavoidably 
unwinds the JVM call stack—unlike native runtimes (V8/Wasmtime, as used by 
Envoy/APISIX) that can use longjmp to preserve exec context. That's why 
TinyGo's wasm-unknown (reactor) target is the correct choice for library-style 
modules on Chicory, just as wasm32-wasip1 + cdylib is the reactor target for 
Rust.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to