Passing Type parameters to functions can cause SIGSEGV

[bojidar-bg]

Passing object of type Type between different FunctionApps running Perper.WebJobs.Extensions causes the receiving instance to segmentation fault whenever it interacts with the Type. Likely related to how Apache Ignite serializes those objects.

PerperTypeBug.zip

namespace Test1
{
    public class TestType
    {
        
    }
}

using Test1;
namespace Test2.FunctionApp
{
    public static class Launcher
    {
        [FunctionName("Launcher")]
        public static async Task Run([PerperModuleTrigger(RunOnStartup = true)]
            PerperModuleContext context,
            CancellationToken cancellationToken)
        {
            await context.StreamActionAsync("Test3.FunctionApp.TestStream.Run", new
            {
                type = typeof(TestType)
            });

            await context.BindOutput(cancellationToken);
        }
    }
}

using Test1;
namespace Test3.FunctionApp
{
    public static class TestStream
    {
        [FunctionName("TestStream")]
        public static async Task Run([PerperStreamTrigger]
            PerperStreamContext context,
            [Perper("type")] Type type,
            CancellationToken cancellationToken)
        {
            Console.WriteLine("{0} {1}", type, typeof(TestType));

            await context.BindOutput(cancellationToken);
        }
    }
}

Output:

Test3> func start --verbose # ... Application started. Press Ctrl+C to shut down. [10/2/2020 9:50:59 AM] Starting 'Test3.FunctionApp.TestStream.Run' as ... [10/2/2020 9:50:59 AM] Executing 'TestStream' (Reason='(null)', ...) sh: “func start --verbose” terminated by signal SIGSEGV (Address boundary error)

Test2> func start -p 7072 --verbose # ... Application started. Press Ctrl+C to shut down. [10/2/2020 9:50:59 AM] Executing 'Launcher' (Reason='(null)', Id=...)