stream-processing

I figured out a way to get the (x,y,z) data points for each frame from one hand previously. but im not sure how to do that for the new holistic model that they released. I am trying to get the all landmark data points for both hands as well as parts of the chest and face. does anyone know how to extract the holistic landmark data/print it to a text file? or at least give me some directions as to h

Is your feature request related to a problem? No

It would be quite useful to convert a panel to/from time-series -> numeric and back. Datadog has this ability in the Edit of a panel and this would be a compelling/competing feature.

Describe the solution you'd like

In the edit options add a type drop-down which will convert the panel to the other type (and in future -> to more possi

Describe the bug
If you try to create a KAFKA formatted source with a BYTES column, the command will return

CREATE STREAM TEST (ID BYTES KEY, b BYTES) WITH (kafka_topic='test', format='DELIMITED');
The 'KAFKA' format does not support type 'BYTES'

This is because the BYTES type is missing [here](https://github.com/confluentinc/ksql/blob/a27e5e7501891e644196f8d164d078672e0feecd

Use try-with-resources or close this "HazelcastServerCachingProvider" in a "finally" clause.

Change the implementation or suppress sonar warning

https://sonarcloud.io/project/issues?fileUuids=AW9qkIoKkrN6v4yKaPtE&id=hz-os-master&resolved=false&severities=BLOCKER&types=BUG

Under the hood, Benthos csv input uses the standard encoding/csv packages's csv.Reader struct.

The current implementation of csv input doesn't allow setting the LazyQuotes field.

We have a use case where we need to set the LazyQuotes field in order to make things work correctly.

I have this implemented in a custom marshaler now but wondering if it makes sense to push back upstream - when we are integrating with legacy services we find it useful to use the correlation ID as the message ID when first brought into watermill - from there they get sent on headers to subsequent services and work normally.

Its a simple change if it would make sense for other users.

If my DataFrame just has 2 rows, and I call df.head(), I get:

Uncaught Error: ParamError: Number of rows cannot be greater than available rows in data
    at DataFrame.head (/.../danfojs-node/dist/danfojs-base/core/frame.js:553:19)

That is not how Pandas behaves. I think just my 2 rows should be returned.

It can be very difficult to piece together a reasonably estimate of a history of events from the current workers logs because none of them have timestamps.

So for that end, I think we should add timestamps to the logs.

This has some cons:

1. We can't just use @printf like we have been until now. We need to either include a timestamp in every @printf call (laborious and error prone) or c

For example, given a simple pipeline such as:

Pipeline p = Pipeline.create();
p.readFrom(TestSources.items("the", "quick", "brown", "fox"))
 .aggregate(aggregator)
 .writeTo(Sinks.logger());

I'd like aggregator to be something requiring a non-serialisable dependency to do its work.

I know I can do this:

Pipeline p = Pipeline.create();
p.readFrom(TestSource

The mapcat function seems to choke if you pass in a mapping function that returns a stream instead of a sequence:

user> (s/stream->seq (s/mapcat (fn [x] (s/->source [x])) (s/->source [1 2 3])))
()
Aug 18, 2019 2:23:39 PM clojure.tools.logging$eval5577$fn__5581 invoke
SEVERE: error in message propagation
java.lang.IllegalArgumentException: Don't know how to create ISeq from: manifold.