Module loading 

Opening a dataset, from the request to its first rows, and its one owner.

[Loader] holds the open in flight ([Load]): its origin, paths, phase, loading screen text, and what it holds (stop flag, footer counter, download, converted IPC file, the generation hold while a download is asked about). The app reports events (a request, a worker’s answer or failure, the user’s download answer) and carries out the [Step] it returns. Nothing else keeps the open’s state.

• Identity. Each load has a [LoadId], carried by its phases’ jobs. An answer is taken only for the load in flight, in the phase that asked; others are dropped with their payload.
• Retirement. Abandoning, replacing or failing a load raises its stop flag (a download or conversion stops at its next chunk and removes its file; a footer pass stops reading), releases its files and its hold.
• Handover. The dataset is built holding the load’s download or converted file and everything found (crate::table::OpenFacts), and takes the footer counter on install; what remains is the first-rows read ([Phase::FirstRows]), whose abandonment stops neither.

Home’s looks, analyses and charts are not loads.

Modules

follow

Following a growing file, as tail -f does: --follow and t at the table.

measurements

What opening a dataset cost, measured rather than guessed: every figure is one datui produced itself (its own listing times, request counts, byte totals). Where Polars reads, datui cannot count, so nothing is recorded; hence the optional fields (see docs/user-guide/dataset-info.md). Written atomically by reading threads, read by the render without blocking.

stdin

Data piped in: cmd | datui and datui -.

tee

--tee FILE: standard input recorded to a file the user keeps, while it is viewed.