tben
fcad4b49d6
The thinking row and the header menu both carry Stop while a bot has work open for the user anywhere: every pending or processing job of that bot in their conversations is failed as stopped, its task closed, a Stopped step recorded and one closing message posted per session, so the thread stops waiting and the bot goes idle. The handler running the job is aborted from this process through a registry, so a job stuck waiting on a model stops at once instead of on its next heartbeat, and a late face change after the abort is dropped. The release stage is now said in the app too: Settings > General reports "Cobble v0.1.5 (alpha)" next to development, and the README and RELEASING.md say what alpha means for installs.
28 lines
922 B
TypeScript
28 lines
922 B
TypeScript
import type { RunningVersion } from "@/src/utils/running-version";
|
|
|
|
/**
|
|
* The stage every release is published as. Cobble is still alpha: the
|
|
* schema, the settings and the screens change between releases, so the app
|
|
* says so wherever it names its version, not only in the README.
|
|
*/
|
|
export const ReleaseStage = "alpha";
|
|
|
|
type Params = {
|
|
running?: RunningVersion | null;
|
|
};
|
|
|
|
/**
|
|
* The running release in words, for the General settings page: "Cobble
|
|
* v0.1.5 (alpha)", and a development server adds that it is one, so a dev
|
|
* build is never mistaken for a release.
|
|
*/
|
|
export default function versionLabel({ running }: Params): string | null {
|
|
if (!running) return null;
|
|
|
|
const parts = [running.mode == "development" ? "development" : "", ReleaseStage].filter(
|
|
(part) => part.length > 0,
|
|
);
|
|
|
|
return `${running.version ? `Cobble ${running.version}` : "Cobble"} (${parts.join(", ")})`;
|
|
}
|