`pipeloom.messages`¶

pipeloom.messages ¶

messages.py¶

Typed message contracts used on the in-memory Queue between worker threads and the single SQLite writer thread.

Why messages?¶

Workers should never touch SQLite directly (SQLite connections are not thread-safe across threads). Instead, workers publish intent via small, immutable dataclasses. The writer is the only component that owns a SQLite connection and it executes the requested changes in a single, serialized place.

MsgTaskStarted `dataclass` ¶

MsgTaskStarted(task_id: int, name: str, started_at: str)

Signal that a task has begun. Posted by a worker thread as soon as the task is admitted for work.

Attributes:

Name	Type	Description
`task_id`	`int`	Unique identifier for the task.
`name`	`str`	Display-friendly name shown in logs and progress UI.
`started_at`	`str`	ISO 8601 UTC string (avoid tz-naive datetimes over queues).

MsgTaskProgress `dataclass` ¶

MsgTaskProgress(task_id: int, step: int, total: int, message: str = '')

Incremental progress signal. The writer translates this into a fractional progress column and updates the Rich bar.

Attributes:

Name	Type	Description
`task_id`	`int`	Unique identifier for the task.
`step`	`int`	Current progress step (1-based).
`total`	`int`	Total number of progress steps.

MsgTaskFinished `dataclass` ¶

MsgTaskFinished(task_id: int, status: str, finished_at: str, result: str | None = None, message: str = '')

Final status + optional result payload for a completed or failed task.

Attributes:

Name	Type	Description
`task_id`	`int`	Unique identifier for the task.
`status`	`str`	Final status of the task ("done" \| "error" \| "cancelled").
`finished_at`	`str`	ISO 8601 UTC string (avoid tz-naive datetimes over queues).
`result`	`str \| None`	Optional result payload for the completed task.
`message`	`str`	Optional status message for the completed task.

pipeloom.messages¶