Task & Timer GClasses - Yuneta Simplified

Async task execution, timers, and counters.

Source: kernel/c/root-linux/src/c_task.c, c_timer.c, c_timer0.c, c_counter.c

C_TASK¶

Task execution engine — orchestrates multi-step jobs with timeout and result handling.

Property	Value
States	`ST_STOPPED`, `ST_IDLE`, `ST_WAIT_RESPONSE`
Input events	`EV_ON_MESSAGE`, `EV_TIMEOUT`, `EV_STOPPED`
Output events	`EV_ON_MESSAGE`

Attribute	Type	Description
`jobs`	`json`	Job definitions (array of steps).
`input_data`	`json`	Input data for jobs.
`output_data`	`json`	Collected output data.
`gobj_jobs`	`pointer`	Gobj that executes jobs.
`gobj_results`	`pointer`	Gobj that receives results.
`timeout`	`integer`	Action timeout in seconds.

High-level timer — recommended for general use. Uses periodic yuno events with millisecond configuration. See the Timer API for helper functions.

Property	Value
States	`ST_STOPPED`, `ST_IDLE`
Output events	`EV_TIMEOUT`

Attribute	Type	Description
`periodic`	`bool`	`TRUE` for recurring, `FALSE` for one-shot.
`msec`	`integer`	Timeout / interval in milliseconds.
`subscriber`	`pointer`	Gobj receiving `EV_TIMEOUT`.

Do not call gobj_start() / gobj_stop() directly — use set_timeout(), set_timeout_periodic(), and clear_timeout().

Low-level timer — uses io_uring directly. Each instance opens a file descriptor. Prefer C_TIMER unless you need lower-level control.

Property	Value
States	`ST_STOPPED`, `ST_IDLE`
Output events	`EV_TIMEOUT`

Same as C_TIMER.

Event counter — tracks incoming events until reaching a target count or a timeout, then fires a final event.

Property	Value
States	`ST_STOPPED`, `ST_IDLE`, `ST_WAIT_COUNT`
Input events	`EV_ON_MESSAGE`, `EV_TIMEOUT`
Output events	custom (`final_event_name`)

Attribute	Type	Description
`max_count`	`integer`	Target event count.
`expiration_timeout`	`integer`	Timeout in seconds (fires even if count not reached).
`final_event_name`	`string`	Event name to fire on completion.
`input_schema`	`json`	Schema for counted events.