Open hossam-nasr opened 1 year ago
cc @davidmrdavid
I get this very same error when setting the flag EnableWorkerIndexing
(not using WebPubSub). My current workaround is setting it blank.
@hossam-nasr: could you please provide guidance on how to deal with this ^. Thanks!
@fchapelle-modjaw Are you using extension bundles in your app? Extension bundles include WebPubSub by default, so this issue will still occur if setting the EnableWorkerIndexing
flag with extension bundles. If you need the EnableWorkerIndexing
flag, then please use an extensions.csproj
file to load only the extensions that you need, instead of using extension bundles.
it's worth noting that EnableWorkerIndexing
is also a preview feature as far as I'm concerned. @fchapelle-modjaw: just so we know, how did you encounter this setting? Did any of the tooling automatically set it for you?
I guess it was added automatically by azure extension for vscode ? Not sure to be honnest.
My requirements.txt is pretty short :
azure-functions
azure-functions-durable
mysql-connector-python
@fchapelle-modjaw I'd say if you don't know why you have it set, then you don't need it, and it's okay to not set it.
There is a bug that sometimes occurs in which running any orchestrator in a DF node app will fail with an error saying "Exception: TypeError: HistoryEvent.init() missing 4 required positional arguments: 'EventType', 'EventId', 'IsPlayed', and 'Timestamp'" as below:
This occurs when:
EnableWorkerIndexing
feature flagMicrosoft.Azure.WebJobs.Extensions.WebPubSub
extension to your.csproj
fileSee this larger issue for more details: https://github.com/Azure/azure-functions-durable-extension/issues/2338