القائمة
Download client torrent lifecycle stages and tag transitions. Use when working on torrent download, processing, or tag logic in app/bin/downloader.py.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Database thread lifecycle stages and transitions. Use when working on thread state queries, scraping logic, or status filtering in app/scrape.py, app/server.py, app/downloader.py.
M-Team scraping workflow, search cursor, rate limiting, and torrent or mediainfo fetch behavior. Use when working on app/scrape.py, app/mt.py, or thread discovery and fetch flow.
FastAPI dashboard routes, daily_stats cache and backfill, thread pages, node pages, and admin APIs. Use when working on app/server.py or dashboard templates.
RPC command queue system for server-to-downloader communication. Use when working on RPC methods, command dispatch, or the /rpc and /api/node/{node_id}/rpc endpoints in app/rpc.py, app/downloader.py, app/server.py.
| name | torrent-lifecycle |
| description | Download client torrent lifecycle stages and tag transitions. Use when working on torrent download, processing, or tag logic in app/bin/downloader.py. |
| user-invocable | false |
Torrents managed by the application go through several stages in the download client (qBittorrent, rTorrent, or Neptune). The lifecycle is determined by torrent state and the process-error tag — NOT by other tags. Tags are purely informational labels to help users see what stage a torrent is in via the client UI.
Tags are defined in app/const.py. They do NOT drive lifecycle logic — they are set/removed alongside state transitions to provide visibility.
| Constant | Value | Description |
|---|---|---|
BT_TAG_DOWNLOADING | downloading | Torrent is actively downloading (set at add time and after resume) |
BT_TAG_FILE_SELECTED | file-selected-4 | File selection has been applied, download limit cleared |
BT_TAG_SELECTING_FILES | selecting-files | Torrent is in paused state waiting for file selection (only on rtorrent) |
BT_TAG_PROCESSING | processing | Download complete, extracting mediainfo |
BT_TAG_PROCESS_ERROR | process-error | Mediainfo extraction failed (exception: this tag IS used in logic to skip retries) |
torrents_add (with tags=[downloading], download_limit=1, sequential)
│
▼
file-selected-4 not in tags → select largest video file (set others priority=0)
Add file-selected-4 tag, clear download limit, resume if paused
│
▼
Downloading... (state is downloading)
Each loop: use t.dlspeed directly → batch update job in PG
│
▼
Download complete (state.is_uploading)
tag: -downloading +processing
│
├── Success: extract mediainfo + check hardcoded subtitles → update thread → torrents_delete
│
└── Failure: tag: +process-error, job marked failed in DB
The code in __process_torrents() determines the stage using torrent state, NOT tags:
__handle_unmanaged_torrent() — tries to reclaim if removed-by-client, otherwise deletesjob.last_progress_at): Removed from client, thread marked torrent_invalid = 'stalled', job marked removed_from_download_client (reason: stalled)state.is_errored): Deleted, job marked failed with "torrent error"process-error tag: Skipped entirely (the one exception where a tag affects logic)state.is_uploading): Swaps tag to processing, runs mediainfo extraction (at most one per __process_torrents() call; remaining uploading torrents wait for the next inner-loop iteration so __pick_and_add_jobs() can run in between)BT_TAG_FILE_SELECTED not in tags): Selects largest video file, clears download limit, adds BT_TAG_FILE_SELECTED tag, resumes if pausedstate.is_paused): Swaps tag to downloading, resumes the torrentt.dlspeed directly (instantaneous speed from BT client), compares current progress against stored job.progress to detect changes, batch-updates job progress/dlspeed/eta in PostgreSQLBT_TAG_FILE_SELECTED not in t.tags__add_torrent() adds torrent with download_limit=1, is_sequential_download=True, tags=[BT_TAG_DOWNLOADING]__fix_file_selection() finds largest video file, sets all other files to priority 0, clears download limit, adds BT_TAG_FILE_SELECTED tagBT_TAG_FILE_SELECTED added, download proceeds at full speed__fix_file_selection() — exceptions bubble up__batch_update_downloading() uses t.dlspeed (instantaneous speed from BT client) directly, compares current progress against stored job.progress to detect changes, batch-updates job progress/dlspeed/eta in PostgreSQL via pipeline mode. Only updates last_progress_at when progress actually changed.job.last_progress_at in PostgreSQL — jobs with no progress update for N+ days are evicted.__maybe_evict_slowest() uses t.dlspeed directly; if total speed < min_download_speed and the slowest torrent has been downloading 24h+, it is evicted.BT_TAG_PROCESS_ERROR tag__process_torrents() phase 3 detects uploading torrents__process_completed_torrent() extracts mediainfo (BDMV or regular), checks hardcoded subtitlesBT_TAG_DOWNLOADING, add BT_TAG_PROCESSINGhard_coded_subtitle, marks job done, deletes torrent + filesBT_TAG_PROCESS_ERROR tag, marks job failed in DBBT_TAG_PROCESS_ERROR in t.tagsIn __process_torrents(), paused torrents are detected and resumed with tag swap (-BT_TAG_SELECTING_FILES +BT_TAG_DOWNLOADING).
job.last_progress_at in PostgreSQL) are removed from client, thread marked torrent_invalid = 'stalled', job marked removed_from_download_client (reason: stalled)state.is_errored are deleted, job marked failed with "torrent error"SELECTED_CATEGORY are deleted, job marked skippedremoved-by-client (reason: "manual")removed-by-clientapp/bin/downloader.py — All torrent processing logic (Downloader.__process_torrents())app/const.py — Tag and status constantsthread-lifecycle skill — Database-side thread state machine