Simon Leet
Simon Leet
Additional observations: - Other webhosts work in the devcontainer to the same ports (e.g. `ng serve` to 8080) - Running `dapr dashboard -k` works, vscode opens a port to `127.0.0.1`....
@leonids2005 Consider creating an issue in dapr/dotnet-sdk for tracking a similar feature if you're interested, I believe these requests are being tracked on a per SDK basis as they have...
I don't think @youngbupark is looking at these issues any more ... @wcs1only @artursouza for their opinion instead.
# Dapr Pub/Sub Batching API Proposal ## Requirements Summarizing some requirements presented from earlier in this issue: - Add an optional parameter `maxBatchSize` defines the maximum number of messages to...
Event Grid diagnostic logs on failed deliveries confirms that Event Grid is getting 404 (not found) from the ngrok endpoint in the failure cases, hence no retries from Event Grid....
The additional logging confirms that the EventGrid service is somehow sending to the message to the wrong URI: From a failed delivery event log: ```json { "time": "2021-11-19T23:46:46.6945198Z", "resourceId": "/SUBSCRIPTIONS/38875A89-0178-4F27-A141-DC6FC01F183D/RESOURCEGROUPS/DAPR2-CONF-TEST-RG/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/DAPR2-CONF-TEST-EVENTGRID-TOPIC",...
Slight note for anyone building off the base images (e.g. base-debian11) instead of cc or core: the `libssl1.1` package control file is provided as `status.d/libssl1` rather than using the correct...
Seems like a reasonable extension of #227 to include user settable IoT Hub system properties.
The existing EventHubs bindings implementation exposes all the `Event.SystemProperties` extracted by the azure-event-hubs-go/v3 SDK, with the expectation that additional properties should be retrievable from the [`Annotations` map](https://github.com/Azure/azure-event-hubs-go/blob/e9f5ac3a5bc593912f87617b22c5ead786d761e1/event.go#L73) but a cursory...