RUNNERNEXT function on standalone

[pi-r-p]

This new function allow to reschedule a runner from the runner itself.

To test, generate a token with this capability:

  'attributes' {
    '.cap:runner.reschedule.min.period' '5000'
  }

Use it with CAPADD inside your runner. From the runner, you can schedule the next iteration to "start of the script" + the period you want:
10 s RUNNERNEXT

It will fail if the requested period is less than the one defined in capability.

The function have no effect on a standalone with remote runner execution, or on a distributed instance.

[pi-r-p]

doc OK. https://warp10.io/doc/RUNNERNEXT

[pi-r-p]

• Fixed overflow if MAXLONG RUNNERNEXT
• introduced RUNNERPROG to schedule at a given time:

"2022-04-09T21:48:00.0Z" TOTIMESTAMP RUNNERPROG

Both combined can allow synchronization on absolute time easily:

"2022-04-09T21:48:00.0Z" TOTIMESTAMP 'startsync' STORE
$startsync NOW >
<%
  MAXLONG RUNNERNEXT
  $startsync RUNNERPROG
%>
<%
  1 h RUNNERNEXT
%>
 IFTE

[hbs]

Should rename the functions RUNNERIN and RUNNERAT

…

On Sat, Apr 9, 2022, 23:58 Pierre Papin ***@***.***> wrote: - Fixed overflow if MAXLONG RUNNERNEXT - introduced RUNNERPROG to schedule at a given time: "2022-04-09T21:48:00.0Z" TOTIMESTAMP RUNNERPROG Both combined can allow synchronization on absolute time easily: "2022-04-09T21:48:00.0Z" TOTIMESTAMP 'startsync' STORE $startsync NOW > <% MAXLONG RUNNERNEXT $startsync RUNNERPROG %> <% 1 h RUNNERNEXT %> IFTE — Reply to this email directly, view it on GitHub <#1088 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABZYMRGXOBZLHCBEA7BSE3VEH4QDANCNFSM5STHAZKA> . You are receiving this because you commented.Message ID: ***@***.***>

[pi-r-p]

Function renamed + $runner.execution.counter added.

Execution counter does not reset when disabling and reenabling the runner, you have to rename the runner.

[pi-r-p]

ready for new review.

[pi-r-p]

ready for new review.

[pi-r-p]

Done. Doc updated.
I will update runner documentation once merged.