Replies: 4 comments 12 replies
-
|
Hi, to make sure the host doesn't crash, you can add a try catch: However, you can't debug a wasm plugin using VS. Instead, you could use Console.Writeline (aka printf debugging). Make sure you enable WASI output to see the logs by seeting https://github.com/extism/extism/tree/main/runtime#environment-variables |
Beta Was this translation helpful? Give feedback.
-
|
I have the try/catch block, but the process terminates before the catch is hit. |
Beta Was this translation helpful? Give feedback.
-
|
hmmm, that shouldn't happen. can you share a repro? P.S: also make sure you have installed the runtime nuget package in the host: https://www.nuget.org/packages/Extism.runtime.all |
Beta Was this translation helpful? Give feedback.
-
|
Sorry I can't share the repo. I can perhaps look to fire up a standalone one, unless you have one with .Net SDK/PDK with Host Functions I can use as a template. What I have is cranked from scratch using the docs - but is explicit to our proprietary use case. Here is the host <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Extism.runtime.all" Version="1.2.0" />
<PackageReference Include="Extism.Sdk" Version="1.2.0" />
</ItemGroup>
</Project>Here is the plugin <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
<RuntimeIdentifier>wasi-wasm</RuntimeIdentifier>
<OutputType>Exe</OutputType>
<PublishTrimmed>true</PublishTrimmed>
<!-- Make sure we create a standalone wasm file for our plugin -->
<WasmSingleFileBundle>true</WasmSingleFileBundle>
<WasmBuildNative>true</WasmBuildNative>
<TrimMode>partial</TrimMode>
<DebuggerSupport>false</DebuggerSupport>
<EventSourceSupport>false</EventSourceSupport>
<UseSystemResourceKeys>true</UseSystemResourceKeys>
<NativeDebugSymbols>false</NativeDebugSymbols>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Extism.Pdk" Version="1.0.2" />
</ItemGroup>
</Project>Is this possibly a runtime issue and how would I know? Should I be using some of the other Env Vars too? Would be great to have all the documentation have code versions for each SDK/PDK - having Every product that uses Extism will have a predominate host language, that we can wrap and provide bindings packages to make it easy for our customer to develop their own plugins in their language of choice, but does not mean we all know or are comfortable in |
Beta Was this translation helpful? Give feedback.
-
Without a repro it's difficult to say, but it should work fine. We use the .NET SDK for running the .NET PDK & SDK tests:
Both csprojs seem fine to me. Can you share a code snippet on how you're calling the plugins (similar to the one I shared with you). You can simplify it and remove the proprietary parts. If you add a try catch around the plugin code, it should NOT crash your host |
Beta Was this translation helpful? Give feedback.
-
|
@mhmd-azeez thanks... Given you reply above, I cloned the SDK repo, and tried to run the tests. I note that some of the If I try and run the |
Beta Was this translation helpful? Give feedback.
-
|
@Simonl9l i have updated the WasmTests project to reference the extism runtime nuget package: You should be able to run the tests on your machine now
For the PDK yes, but the SDK supports lower versions too. These projects are not using the Extism PDK |
Beta Was this translation helpful? Give feedback.
-
|
@mhmd-azeez thanks again, I pulled the latest I had to fix this reference to point to Debug (than Release): private string GetWasmPath(string name)
{
return Path.Combine(
Environment.CurrentDirectory,
$"../../../../../samples/{name}/bin/Debug/net8.0/wasi-wasm/AppBundle/{name}.wasm");
}However even with that it explodes wih the logging saying
To confirm I'm running on an Apple Silicon under under MacOS. This is expected to work? |
Beta Was this translation helpful? Give feedback.
-
By default the host functions are expected to be in the
Okay, let us know if you run into any other issues |
Beta Was this translation helpful? Give feedback.
-
|
So for arguments sake, should my plugin host itself be an assembly (as sub assembly) that it not part of the executable host but referenced in the project, but arguably would be if AoT'd, do I need to do anything different with this DllHost name, and per the code in the test why is it Also would the be a case of the When I run the As running these seem to make the test work that was not otherwise done just running the tests. |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
I am not sure if I understand this. But in the case of the PDK, the
You should get an exception, not a crash
The PDK uses an MSBuild task to generate some glue code necessary for making exports work. Right now .NET doesn't have an easy way of exprorting functions for wasi. So we had to build our own MSBuild task. This is an implementation detail |
Beta Was this translation helpful? Give feedback.
-
|
OK thank again for following up.
so my use of the DllName of [DllImport("extism", EntryPoint = "End")] private static extern void End(ulong messageOffset);where the corresponds to a hist function defend as follows: new HostFunction(
"End",
[/* Message */ ExtismValType.PTR,],
Array.Empty<ExtismValType>(),
IntPtr.Zero,
(plugin, inputs, _) =>
{
var message = plugin.ReadString(inputs[0].v.ptr);
var task = _sink.End(message); // a bit of the impl. - sends the message on.
Task.WhenAll([task]).ConfigureAwait(true);
}),This is in a separate referenced assembly, whist not currently AoT'd, will be.
Still Crashing...still don't know why!
To confirm this is all part of what's built into the PDK assembly/package, and nothing we need to do here when building and hosting plugins. Or do we need to do something here - is so where is this documented? |
Beta Was this translation helpful? Give feedback.
-
Yes, this seems correct
I'd be careful about using Tasks inside host functions. Since the callback is not async, exceptions are probably not being propagated properly. Maybe this is the source of the crash?
Exactly, this is just an implementation details and you shouldn't need to worry about it |
Beta Was this translation helpful? Give feedback.
-
If I am using the .Net Host SDK and the .Net PDK, (including host functions) is there a way to debug the plugin?
Both are in the same solution, but breakpoints in the plugin/PDK implementation won't activate.
I'm also using Rider but that should not make any difference?
when I try in invoke a method on the plugin the process terminates with zero error reporting.
The explosion happens when the
LibExtism.extism_plugin_callis invoked.Beta Was this translation helpful? Give feedback.
All reactions