Open Furrman opened 1 month ago
I am having same issue as well so looks like SignalR has not caught up with recent .NET8 upgrades
I was just going to post something similar, Im also seeing this issue.
I have did investigation on your source code and looks like you are passing the return object to the Sytem.Threading.Channels library in GrpcWorker:ProcessRequestCoreAsync() to send it over to the client side. I cannot go further but seems something there is ignoring our return object. It can be wrong assigment or anything, but it is outside of my reach. There is one more thing that got my attention that in your main branch, in DotNetWorker.Grpc project, you do not have setup .net8 dedicated packages - instead you refer to System.Threading.Channels to 6.0.0 version in your .NETStandard references. I checked and the newest package version is 8.0.0 which has high probability it is the version prepared for .NET8. Can it be related to this issue? Maybe updating reference would fix the problem we are facing? At last I can add, that our codebase with working solution was using Microsoft.Azure.WebJobs.Extensions.SignalRService package instead (for in-process mode in function app).
Can someone from admins add label potential-bug and need-attention?
Hi,
Has anyone seen any updates on this issue being investigated?
This is also impacting my live project and preventing me from upgrading to .NET8, so I'm eager for this to be resolved asap.
Thanks.
@Y-Sindo Is this something you can help look into?
@satvu This is a known issue, see #1496 . Please see #1496 to track the progress.
What version of .NET does your existing project use?
.NET 6
What version of .NET are you attempting to target?
.NET 8
Description
Hello,
I wanted to bring up an issue with the SignalRTrigger solution. My team and I are using this approach in .NET6 for our project to trigger some asynchronous operations. In response, we are returning a custom object indicating whether the operation was successful. However, in .NET8, our SignalRTrigger functions consistently return a null result in the server response, regardless of our efforts to fix it. It is worth mentioning that during the .NET8 upgrade, we are migrating our functions to isolated mode.
Expected
Function with SignalR trigger and return type will send custom response in result field to client.
Actual
Function with SignalR trigger is sending null result to client.
Examples
Click me
Here is our server-side code in .NET6: ``` [SignalRHub(path: "")] public partial class MainHub : ServerlessHubLink to a repository that reproduces the issue
https://github.com/Azure/azure-functions-dotnet-worker/tree/main/samples/Extensions/SignalR