Skip to content

feat: add persistent generation sessions with exclusive turns - #2

Draft
giaan1702 wants to merge 2 commits into
suncodevn:mainfrom
giaan1702:feat/sessions
Draft

giaan1702 wants to merge 2 commits into
suncodevn:mainfrom
giaan1702:feat/sessions

Conversation

@giaan1702

Copy link
Copy Markdown

Related to #1.

Related image/video jobs currently create independent upstream threads. This adds an opt-in generation_session_id so sequential jobs can retain one thread and account, with exclusive turns and a conservative uncertain state after ambiguous failures. Requests without the field keep the existing behavior.

Includes session create/inspection endpoints, ownership checks, persistence, dispatcher integration, previous-turn media filtering, OpenAPI definitions, usage documentation, and six regression tests. Session jobs do not automatically retry or fail over to another account.

Validation: 30/30 architecture + Studio tests pass; syntax check passes for 66 files; git diff whitespace check passes. Tests use offline fixtures/local HTTP servers. No new paid generation was submitted, and MongoDB crash recovery/distributed load were not rerun.

Draft for design review: retention/close/reconciliation APIs are not implemented; interrupted-turn and multi-node behavior need further integration review. See docs/generation-sessions.md. This PR is independent of the multi-reference proposal and does not include ComfyUI connector or machine-specific configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant