mirror of
https://github.com/tiennm99/DocsGPT.git
synced 2026-10-04 10:13:06 +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.
38 lines
1.3 KiB
Python
38 lines
1.3 KiB
Python
"""Shared helpers for connector auth modules.
|
|
|
|
These helpers exist so that sensitive values (session tokens, bearer
|
|
credentials) never end up interpolated into exception messages or log
|
|
lines. Exception messages frequently flow into ``stack_logs`` (Postgres)
|
|
and Sentry via ``exc_info=True``, so the raw value must never be the
|
|
thing we format.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
import hashlib
|
|
|
|
|
|
def session_token_fingerprint(session_token: str) -> str:
|
|
"""Return a short, irreversible fingerprint for a session token.
|
|
|
|
The returned string is safe to embed in exception messages and log
|
|
lines: it is a prefix of a SHA-256 digest, clearly tagged so an
|
|
operator reading the log knows it is a hash and not the token
|
|
itself. It is stable for a given input, which lets operators
|
|
correlate "which token failed" across log lines without exposing
|
|
the credential.
|
|
|
|
Args:
|
|
session_token: The raw session token. Accepts ``None`` or the
|
|
empty string for defensive callers; both yield a distinct
|
|
sentinel rather than raising.
|
|
|
|
Returns:
|
|
A string of the form ``"sha256:<6 hex chars>"``, or
|
|
``"sha256:<empty>"`` when the input is falsy.
|
|
"""
|
|
if not session_token:
|
|
return "sha256:<empty>"
|
|
digest = hashlib.sha256(session_token.encode("utf-8")).hexdigest()
|
|
return f"sha256:{digest[:6]}"
|