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

Unable to Debug Durable Entities on local machine #361

Closed
harrict opened this issue Mar 8, 2024 · 2 comments
Closed

Unable to Debug Durable Entities on local machine #361

harrict opened this issue Mar 8, 2024 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@harrict
Copy link

harrict commented Mar 8, 2024

I'm trying to use Netherite with a durable function that also utilizes durable entities. The function app is a .NET 8 isolated function. I am trying to ensure the functionality works before publishing to Azure but when I test locally I get an error when calling any of the durable entity methods. When calling either SignalEntityAsync or CallEntityAsync I get an NullReferenceException at DurableTask.Core.Entities.OrchestrationEntityContext.AdjustOutgoingMessage. The null reference seems to be for this.innerContext.EntityParameters.EntityMessageReorderWindow.

More details:

  • I tested the function not using Netherite, just using Azure Storage, and it works fine
  • I've tried both Memory and SingleHost emulation modes as well as pointing directly to an event hub resource but still get the same error
  • The entity is a basic counter entity that is a copy of the example on microsoft's site
@sebastianburckhardt
Copy link
Member

Sorry about this. In fact, this behavior is consistent with known bugs / limitations.

There are two problems here currently:

@sebastianburckhardt sebastianburckhardt added duplicate This issue or pull request already exists and removed Needs: Triage 🔍 labels Mar 18, 2024
@sebastianburckhardt sebastianburckhardt added this to the 1.5.1 milestone Mar 18, 2024
Copy link
Contributor

This issue has been marked as duplicate and has not had any activity for 1 day. It will be closed for housekeeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants