Chris Sung

@mrrobot47 would this get merged anytime soon? I'm having trouble running it in arm64 architecture.

for anyone end up search arm64 here, feel free to use https://github.com/christallire/action-slack-notify/pkgs/container/action-slack-notify

I've feeling that this issue is related to (https://github.com/elastic/ecs-dotnet/issues/168#issue-1038641469) because the internal serializer might be different than serilog's one, which causes this bug. I think the log should be human...

Yup, I've expected that. since the dawn of .net core arm64 support, I've been poking everywhere around to get arm support ASAP👍🏿

see my analysis 2022년 5월 6일 (금) 오후 11:05, Reuben Bond ***@***.***>님이 작성: > Do you know the root cause for the failure? > > — > Reply to this...

It's a bit complicated to show you since it's part of the internal framework and all start-up logic is split into several classes. edit: builder ``` builder.UseKubernetesHosting() .UseAdoNetClustering(options => {...

here you go: https://gist.github.com/christallire/269fc4ba25c73be1df53b983f6924244

@ismaelhamed yes, your code is what I meant. we need to stash everything to achieve what I want and why don't we just simply support async delegate in persist(...) instead...

Do you mean `ReceiveActor` an anti-pattern compared to akka-typed? Anyways, thanks for your workaround. I am also suggesting to add async callback overload, https://github.com/akkadotnet/akka.net/issues/2197 this approach seems to be better....

Another thing I noticed Is that an authorization check (the route with [Authorize] Attribute) is done before the component lifecycle or Routing. For an example. I used to put OnInitialized...