event-driven

Require GitHub tags to be signed as per https://github.com/ossf/scorecard/blob/main/checks/checks.md#signed-tags

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

The resource name and the queue endpoint suffix should be configurable in triggers.

https://github.com/kedacore/keda/blob/57ffd4ee384db38f1169453cb16b31f00eacffa5/pkg/scalers/azure/azure_storage.go#L34-L64

Task List

• #1921
• #1916
• #1915
• #1917
• #1918
• #1920
• #1919

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

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

Describe the bug

The response of MongoDB is inconsistent wrt to SQL databases if the schema has links of type array. When the nested table doesn't have any rows/documents in it. The response returned is different

Expected behaviour

Actual behaviour

Steps to reproduce

• Fire the query & observer the result

link table as array
if nested table has no rows, postgres 

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

Describe the bug
A clear and concise description of what the bug is.

In Trigger Lifecycle specification, it specify the following:

If the Trigger's `spec.delivery.deadLetterSink` field it set, it MUST be resolved to a URI and reported in `status.deadLetterSinkUri` in the same man

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

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.