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

Bug description

Please describe.
If this affects the front-end, screenshots would be of great help.
in the development environment if we make any change. change is not reflected over the browser

Expected behavior

change should be reflected immediately without manually refreshing the page

How to reproduce

you can change any text

Thank you for your bug repor

This test throws NPE:

public class TestSlowAsyncMapper {
    @Test
    public void foo() {
        var hz = Hazelcast.newHazelcastInstance(newConfig());
        hz.getJet().newJob(newPipeline()).join();
    }

    private Pipeline newPipeline() {
        var p = Pipeline.create();
        p.readFrom(TestSources.itemStream(Integer.MAX_VALUE))
                .withNativeTimestamp

MySQL and Postgres support the \G modifier at the end of a query to present output in a vertical format instead of a horizontal one. It's supremely useful when you have a lot of columns. We should adopt the same.

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

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