You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a strange behaviour where the timestamp is not being evaluated too early for the first 3 elements, then afterwards the timestamp works as expected.
This behaviour is reproducible via the following snippet:
The expected outcome is that the time property should be offset by ~5 seconds for each entry, where as the following clearly shows that the time is not uniformly distributed:
Investigating the issue and the root cause is that the body template is evaluated when the job is added to the queue and not when the request is sent. This leads to the timestamps being unpredictable when using with delay and delayBefore flags.
There might be a way to delay the evaluation of the body though this will likely be a more complex change (which will take longer).
Until this is fixed, then c8y util repeat --delay 5s before the c8y events create (or creating any body using a template)
There is a strange behaviour where the timestamp is not being evaluated too early for the first 3 elements, then afterwards the timestamp works as expected.
This behaviour is reproducible via the following snippet:
The expected outcome is that the
time
property should be offset by ~5 seconds for each entry, where as the following clearly shows that the time is not uniformly distributed:The text was updated successfully, but these errors were encountered: