Josh van Leeuwen

@jxs1211 this typically means that you haven't registered the middleware like so: https://github.com/dapr/dapr/blob/1a3257d2cbd71e6cae7b438b470e5332a23cbaf3/cmd/daprd/components/middleware_http_bearer.go#L29 Don't forget you will need to use the correct build flag to include the file for compilation...

> change to custom middleware annotations, change back to original annotation failed with the error How are the annotations being changed? It is not the case you can _update_ the...

@jxs1211 dapr is ingesting the Component `tintin-authz` which has a type `middleware.http.authz ` which does not exist in upstream dapr

> > [@jxs1211](https://github.com/jxs1211) dapr is ingesting the Component `tintin-authz` which has a type `middleware.http.authz ` which does not exist in upstream dapr > > Yes, that's the fact, but I...

We should try and squat this port earlier in the runtime startup

Hi both. I have verified with the following integration test that overwriting an actor reminder, with both the HTTP and gRPC clients will not cause an error/non-200 response. There will...

@danielgerlag is the Dapr control plane (scheduler) running with version v1.16?

@WhitWaldo upon an error the SDK must report that the workflow is in a FAILED state. This is a responsibility of the SDK implementation to bubble the error to the...

UPDATE: Due to the nature of the current implementation of write through caching of actor state and the unavailability of the real TTL expire time of state keys, SDKs will...

> @JoshVanL We might just be able to keep this one closed - in the responses to a [similar ticket](https://github.com/dapr/dotnet-sdk/issues/1533) in the .NET SDK, @olitomlinson pointed out the reasonableness of...