Hi, I'm a starter and trying to learn how to customize or modify my own mediapipe line. I used Neural Networks to train landmarks which extract from mediapipe. Is there any way I can put my trained model back to mediapipe to implementing real-time gesture recognition？Thanks for your help.

Checklist

• I have included information about relevant versions
• I have verified that the issue persists when using the master branch of Faust.

Steps to reproduce

Given one Faust Table, two topic Agents:

partition_no = 4

topic_1 = app.topic('topic_1', partitions=partition_no, internal=True)
topic_2 = app.topic('topic_1', key_type=str, value_type=InfoDetai

Azure Event Hubs is like a managed Kafka service:

Allow existing Apache Kafka clients and applications to talk to Event Hubs without any code changes—you get a managed Kafka experience without having to manage your own clusters.

This suggests that we could wrap the existing kafka sink. I'd prefer that we wrap it since it is techni

Is your feature request related to a problem? Please describe.

If I have a schema that is in schema registry but is not under the correct subject name, I cannot specify my KSQL stream to use that topic with AVRO format.

Describe the solution you'd like
We should support specifying AVRO_SCHEMA_ID in the WITH clause of create statements.

**Describe alternatives you've consider

We use http_server as input and http_client as one of outputs (for a part of message batch). In case when there is some error coming from http_client, benthos starts to retry this error message indefinitely (#415). However most significant, is that it stops accepting other, normal messages.

Here is the log when I first try to send message which causes http_client to get 500 error, and

I am using this code directly from the documentation. However is not not working, since I am getting:

ERROR: unrecognized configuration parameter "stream_targets"

CREATE FOREIGN TABLE stream (x integer, y integer) SERVER pipelinedb;
CREATE VIEW v0 AS SELECT COUNT(*) FROM stream;
CREATE VIEW v1 AS SELECT COUNT(*)

Currently, you are not able to use middleware per handler in "clean way" (you can still manually wrap the handler function, or have separated router).

It would be nice to be able to add middleware per handler.

As a good reference point, you can use chi router: https://github.com/go-chi/chi

Bug Report

The [STREAM_TASK] configuration block was documented for v1.3, but I'm unable to find documentation for this in the v1.4 docs.

It would be useful to see how riko compares to other stream processors. Possible metrics to track are open sockets, bandwith, CPU, and memory usage.

Wallaroo applications are composed of distinct stages. A state computation stage corresponds to what is called a "step group", which is made up of all the steps holding keys related to that stage. This distinction should be described in the code, since it is difficult to infer from the related comments that are currently scattered around unless you really knew what you were looking for.

Description:
Time to time we get questions from users on how to do various tasks in Siddhi, and we use to answer those questions in StackOverflow and slack. But there should be a commonplace where users can find and learn about all that Siddhi can do.

Approach
One option is to update the Siddhi query guide, but having random examples in the language guide can dilute the purpose. There

com.alibaba.fastjson.JSONException: syntax error, error
at com.alibaba.fastjson.parser.DefaultJSONParser.parseObject(DefaultJSONParser.java:600)
at com.alibaba.fastjson.parser.DefaultJSONParser.parse(DefaultJSONParser.java:1394)
at com.alibaba.fastjson.parser.DefaultJSONParser.parse(DefaultJSONParser.java:1360)
at com.alibaba.fastjson.JSON.parse(JSON.java:165)

As a continuation of the bug reported at spring-cloud/spring-cloud-dataflow-ui#1387, it'd be good to add an explicit endpoint to retrieve the relevant information in 1 call.

According to https://cloud.spring.io/spring-cloud-static/spring-cloud-stream/current/reference/html/spring-cloud-stream.html#_annotation_based_support_legacy and the javadoc of @StreamListener the annotation-based configuration is deprecated and will be removed in the future.

However, according to https://cloud.spring.io/spring-cloud-static/spring-cloud-stream-binder-kafka/current/reference/htm

Currently the syntax is like jet -a <address> -n <name> submit <jar> .. which looks rather odd. We should allow adding address/name after the commands as well.

There might be a few conflicts because -n in submit command is already used for other parameters.

All exceptions in namespace JsonMachine\Exception should extend one common exception, say JsonMachineException, so that userland code can catch for only one type and catch anything from this library. Fell free to create pull request and participate :)