DarkHelm.org/plex-playlist
Public Access
4
0
Fork 0
Code Issues 56 Pull Requests 1 Actions 11 Packages Projects 1 Releases Wiki Activity

TASK: Harden transaction boundaries and race handling #52

New Issue
Open
opened 2026-05-15 17:36:34 -04:00 by darkhelm · 0 comments
darkhelm commented 2026-05-15 17:36:34 -04:00
Owner
Copy Link

Parent

#9

What to build

Eliminate race paths in replacement/generation through locking and transaction strategy.

Acceptance criteria

  • Concurrent replacement/generation races are identified
  • Transaction/locking approach is implemented
  • Race-focused tests validate stability

Blocked by

Notes

  • Python backend code must be fully typed and async-safe.
  • Any blocking work must be wrapped through thread/process execution paths as appropriate.
  • Must pass lint, format, typing, docstring, and test quality gates.
## Parent #9 ## What to build Eliminate race paths in replacement/generation through locking and transaction strategy. ## Acceptance criteria - [ ] Concurrent replacement/generation races are identified - [ ] Transaction/locking approach is implemented - [ ] Race-focused tests validate stability ## Blocked by - #38 ## Notes - Python backend code must be fully typed and async-safe. - Any blocking work must be wrapped through thread/process execution paths as appropriate. - Must pass lint, format, typing, docstring, and test quality gates.
darkhelm added this to the v1 Dynamic Realtime Playlist milestone 2026-05-15 17:36:34 -04:00
darkhelm added the backendrealtimeafktask labels 2026-05-15 17:36:34 -04:00
darkhelm added this to the Main Project Board project 2026-05-15 17:48:59 -04:00
darkhelm removed this from the Main Project Board project 2026-05-15 17:52:20 -04:00
darkhelm modified the milestone from v1 Dynamic Realtime Playlist to E8 - Hardening, Performance, and Release Readiness 2026-05-15 17:55:03 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
afk
Autonomous-friendly issue
 algorithm
Selection logic
 api
API contract
 backend
Backend related
 database
Database related
 devex
Developer experience
 docs
Documentation
 epic
Top-level planning item
 frontend
Frontend related
 hitl
Requires human-in-the-loop decision
 ingestion
Ingestion/sync
 ops
Operations
 performance
Performance
 realtime
Realtime/eventing
 release
Release readiness
 security
Security
 task
Implementation ticket
 testing
Testing
 ui
UI/UX
No Label afk backend realtime task
Milestone
No items
No Milestone E8 - Hardening, Performance, and Release Readiness
Projects
Clear projects
No project
Assignees
Clear assignees
copilotcoder darkhelm renovate-bot repository-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DarkHelm.org/plex-playlist#52
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?