Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SignalRService crashes with "Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0" #2833

Open
pingu2k4 opened this issue Nov 6, 2024 · 1 comment
Assignees
Labels
extensions: signal-r needs-investigation potential-bug Items opened using the bug report template, not yet triaged and confirmed as a bug

Comments

@pingu2k4
Copy link

pingu2k4 commented Nov 6, 2024

Description

Everything compiles fine, and runs fine. But the moment you trigger something with a SignalROutput binding, you will see the error claiming it cannot find System.Memory.Data.

Running it again from this point will crash the functions host on startup with the same error.

Highly linked to Azure/azure-functions-host#10575, however as this is the repo specific for Microsoft.Azure.Functions.Worker.Extensions.SignalRService I figured an issue should represent it here too.

This effects 1.15.0, whereas 1.14.1 works.

I have tried all the common workarounds, like adding <_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput> to the csproj, and in this instance none of them resolve the issue. Only reverting to 1.14.1.

Steps to reproduce

  • Include Microsoft.Azure.Functions.Worker.Extensions.SignalRService
  • Write a simple function with SignalROutputTrigger
  • Invoke the function
  • Observe the error
  • restart functions
  • observe the error on startup
@pingu2k4 pingu2k4 added the potential-bug Items opened using the bug report template, not yet triaged and confirmed as a bug label Nov 6, 2024
@fabiocav
Copy link
Member

fabiocav commented Nov 7, 2024

Thank you for the report here, @pingu2k4. I have updated the original issue on the host side and we're working to delist the impacted packages while the root cause is addressed.

Will keep this issue open while those changes are in progress.

In the meantime, downgrading the extension reference should address what you're seeing.

Thanks again for the report and patience with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensions: signal-r needs-investigation potential-bug Items opened using the bug report template, not yet triaged and confirmed as a bug
Projects
None yet
Development

No branches or pull requests

4 participants