mirror of
https://github.com/tiennm99/DocsGPT.git
synced 2026-10-04 12:13:05 +00:00
Alex
574f96341e
The backend import package is now docsgpt, the name it will carry on PyPI; application was far too generic to install into anyone's site-packages. git mv plus a mechanical rewrite of every import, dotted string and path reference: 734 Python files, the compose files, Dockerfile, workflows, docs, setup scripts, devcontainer, k8s manifests, vscode config, pytest and coverage config, .gitignore. Behaviour is unchanged. Kept for one release: - A top-level application package whose meta-path finder resolves application.x.y to the already-imported docsgpt.x.y object, so old imports and entry points (celery -A application.app.celery, uvicorn application.asgi:asgi_app) keep working with a FutureWarning. - Celery registers every application.* task name as an alias of its docsgpt.* task on start-up, so messages queued by the previous release still run. The redbeat key prefix moves to redbeat:docsgpt:v2: so schedule entries the previous release wrote are left unread instead of firing twice. The backend image builds from the repository root (docker build -f docsgpt/Dockerfile .) so it can ship the alias package; a root .dockerignore allow-lists docsgpt/ and application/ and keeps caches, local data, .env files, the sample index files and the Dockerfile out. Compose and the image workflows point at the new context.
45 lines
1.7 KiB
Python
45 lines
1.7 KiB
Python
"""Resolve whether an answer is persisted and whether it lists in the sidebar.
|
|
|
|
Persistence (is a row written at all?) and visibility (does it show in the
|
|
owner's sidebar?) are separate decisions. Conversations persist by default
|
|
everywhere, and visibility defaults to ``hidden`` for every caller: only an
|
|
explicit request-level ``visibility: "listed"`` — which the first-party UI
|
|
sends on normal chats — puts a conversation in the owner's sidebar. The
|
|
legacy ``save_conversation`` flag no longer affects either decision, so
|
|
API/OpenAI-compatible clients that still send it (its old meaning was
|
|
"persist this conversation") can't list rows into the agent owner's sidebar.
|
|
"""
|
|
|
|
from typing import Any, Optional, Tuple
|
|
|
|
VISIBILITY_LISTED = "listed"
|
|
VISIBILITY_HIDDEN = "hidden"
|
|
|
|
|
|
def resolve_persistence(
|
|
*,
|
|
visibility_flag: Optional[Any] = None,
|
|
persist_flag: Optional[bool] = None,
|
|
) -> Tuple[bool, str]:
|
|
"""Resolve ``(should_persist, visibility)`` for an answer request.
|
|
|
|
Args:
|
|
visibility_flag: Request-level ``visibility`` value. Only the exact
|
|
string ``"listed"`` opts the conversation into the owner's
|
|
sidebar; anything else (including ``None``) stays hidden.
|
|
persist_flag: Explicit persistence opt-out (``False`` to skip writing
|
|
a row, e.g. stateless tool rounds that would orphan one). ``None``
|
|
keeps the always-persist default.
|
|
|
|
Returns:
|
|
``(should_persist, visibility)`` where ``visibility`` is
|
|
``"listed"`` or ``"hidden"``.
|
|
"""
|
|
should_persist = True if persist_flag is None else bool(persist_flag)
|
|
visibility = (
|
|
VISIBILITY_LISTED
|
|
if visibility_flag == VISIBILITY_LISTED
|
|
else VISIBILITY_HIDDEN
|
|
)
|
|
return should_persist, visibility
|