simpletime | Get manipulated time values | Date Time Utils library

Below you'll find a minimal complete Camel 3 (version 3.4.3) example how to trigger a route (TimerRoute) with Timer component and how to call another route (SaveFileRoute). The example is implemented with Camel Main module.

The routes use From EIP to consume messages from endpoints generated by Timer and Direct components and To EIP to produce (or "to send") messages to the consumers.

First the Timer component is used to automatically generate route invocations. This is the starting point of the message flow:

You can merge the notifier with the original stream and get the result from there try the example below.

Yes, you're on the right track.

await simpleTimer(callback) will wait for the Promise returned by simpleTimer() to resolve so callback() gets called the first time and setTimeout() also gets called. jest.useFakeTimers() replaced setTimeout() with a mock so the mock records that it was called with [ () => { simpleTimer(callback) }, 1000 ].

jest.advanceTimersByTime(8000) runs () => { simpleTimer(callback) } (since 1000 < 8000) which calls setTimer(callback) which calls callback() the second time and returns the Promise created by await. setTimeout() does not run a second time since the rest of setTimer(callback) is queued in the PromiseJobs queue and has not had a chance to run.

expect(callback).toHaveBeenCalledTimes(9) fails reporting that callback() was only called twice.

This is a good question. It draws attention to some unique characteristics of JavaScript and how it works under the hood.

Message Queue

JavaScript uses a message queue. Each message is run to completion before the runtime returns to the queue to retrieve the next message. Functions like setTimeout() add messages to the queue.

Job Queues

ES6 introduces Job Queues and one of the required job queues is PromiseJobs which handles "Jobs that are responses to the settlement of a Promise". Any jobs in this queue run after the current message completes and before the next message begins. then() queues a job in PromiseJobs when the Promise it is called on resolves.

async / await

async / await is just syntactic sugar over promises and generators. async always returns a Promise and await essentially wraps the rest of the function in a then callback attached to the Promise it is given.

Timer Mocks

Timer Mocks work by replacing functions like setTimeout() with mocks when jest.useFakeTimers() is called. These mocks record the arguments they were called with. Then when jest.advanceTimersByTime() is called a loop runs that synchronously calls any callbacks that would have been scheduled in the elapsed time, including any that get added while running the callbacks.

In other words, setTimeout() normally queues messages that must wait until the current message completes before they can run. Timer Mocks allow the callbacks to be run synchronously within the current message.

Here is an example that demonstrates the above information:

Add ngx like this:

My SwingWorker is for counting time, it will update time every 1 second.

If the only responsibility of this worker is to update a label with the elapsed time, then a Swing Timer is a better candidate to do it. Let the SwingWorker doInBackground() implementation do the heavy calculation and finally the done() implementation may just stop the timer and display the final results.

Do not call Thread.sleep() in the EDT because it will freeze the entire GUI event processing and you'll probably see just the final result without the intended periodic updates.

Adding just a simple snippet to start with:

It sounds like it could be caused by your Python program. Did you remember to add a null-terminator (\0) after the 1234 integer? Serial commands generally require strings, which must end with a null-terminator. If not your Arduino might keep on waiting for the terminator, and only stops when a timeout occurs or watchdog causes a reset (which could be 4 seconds). That would explain the hold-up.

It doesn't seem to be possible, if you take a look at the "GitHub: ng2-simple-timer-example", directly from the docs, you'll find how the author deals with multiple timers; I won't quote all the code, you can look at it yourself, but just paste here the way callbacks are handled:

Even if this question is downvoted, I will post my results here:

The measured/calculated/interpreted value seems to be correct. THX for reading.

Anyway: I would prefer a more detailed and mathematical documentation of the prometheus methods.

Its just wrong docs. Those lifecycle hooks fire regularily for directives also. Wouldn't make too much sense otherwise.

Ref: https://github.com/angular/angular/issues/10221