event-driven

The feature ask - expose Dapr runtime version in the Metadata API: https://docs.dapr.io/reference/api/metadata_api/

There are certain scenarios where apps would like to check that they are running within a tested Dapr version.

If you want to work with a complete socket address type including port, we have a helper in SocketAddress. However, the moment you want to talk only about an IP address we force you to hold an in_addr or in_addr6 structure: hardly the friendliest versions of these data types.

We should provide a helpful wrapper IPAddress type that can be converted into those types as needed. This would

Proposal

As disscuseed on kedacore/keda#2765 (comment), we should unify the functions for Status & Conditions handling. Referencing controller related stuff here is suboptimal.

There are two locations with similar functions:
https://github.com/kedacore/keda/blob/9f0ee58fc6839d74636e1ec6883fe21d82617ea3/controllers/keda/util/status.go#L30-L63
https://g

For an implementation of #126 (PostgreSQL driver with SKIP LOCKED), I create a SQL table for each consumer group containing the offsets ready to be consumed. The name for these tables is build by concatenating some prefix, the name of the topic and the name of the consumer group. In some of the test cases in the test suite, UUID are used for both, the topic and the consumer group. Each UUID has

Correct me if I'm wrong, but it seems to me that different effector-vue APIs (especially Options API vs. Hooks API) assume different Vue versions.

For example, I tried to use Hooks API in combination with Vue 2 & @vue/composition-api but it won't compile because it tries to import composition functions directly from vue module (as in Vue 3) instead of @vue/compositon-api module (as in V

The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi

我看到可以通过Prometheus搭建监控环境，如果有图文，更容易理解．

Receive events from MSK with IAM auth config https://docs.aws.amazon.com/msk/latest/developerguide/iam-access-control.html

I know it's not a course about RESTful principles but maybe you'll consider in the future extracting resource id from request body to path parameter ?

https://github.com/aspnetrun/run-aspnetcore-microservices/blob/c30712aa099bc335f5613a3b196ea1e943f800a5/src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs#L85

Problem

I'm getting this warning on k8s 1.23:

Warning: autoscaling/v2beta2 HorizontalPodAutoscaler is deprecated in v1.23+, unavailable in v1.26+; use autoscaling/v2 HorizontalPodAutoscaler

on

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z"

Search before asking

• I had searched in the issues and found no similar issues.

Documentation Related

There is a missing file eventmesh-runtime/conf/rocketmq-client.properties which is required to deploy eventmesh-runtime in master branch

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Currently, WebSocket is working for client/server side. However, the browsers do not allow to create tcp connections direclty (which is the current implementation based). Instead, the web-sys must be used.

• Use a different WebSocket implementation if the target is wasm.
• wasm example of a client.