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

Description

1. The theme change toggle's placement is incorrect as it is being placed at the most important place i.e. top left, ideally it should be place in the top right as it's not the highlight of the product.

2. There

I have a use case where I need to create a new stream containing the bearing between two consecutive points in a pre-existing lat/lon stream. Normally bearing would be available in a standard lib but in a pinch can easily be implemented through sin, cos, and atan2 funcs, none of which are currently available in ksql.

Basic trig functions have a range of use cases in geometric and geographic co

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.

Is your feature request related to a problem? Please describe.
Would it be possible to get the support of the weekNumber function in Datetime

Describe the solution you'd like
For a given date, it should return the number of the week in the year, from 1 to 52/53 (or 0 to 51/52).

Thanks

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.