You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Client saved-connection records as one state machine (#4925) #4973
Keep one table as data for save, observe, claim, migrate, replace, and remove. Define each transition's owner check, record update, and failure result.
Preserve the distinct records for case variants and the read-only behavior of status. Serialize legacy alias claims across processes before disconnect or replacement tears down a connection.
Preserve the exact session owner's stored scope during migration. Use a lossless identity for new scope derivation.
Verification
Exercise concurrent save, disconnect, and migration with case variants and invalid or unreadable legacy files. Verify that a stale client cannot remove another session's record or release its lease.
Related work
Follow #4925. Reuse the scope and serialization work in #4946. Schedule this after the daemon migration.
The issue requests implementing saved-connection records as a single transition-owner state machine with specific behavior and verification requirements. This describes new/refactored behavior, not a defect, and provides enough scope for maintainers to act on it.
Activity
apex-sentinel-staging commentedon Nov 22, 2026
Apex Sentinel · Issue review
Suggested label:
featureThe issue requests implementing saved-connection records as a single transition-owner state machine with specific behavior and verification requirements. This describes new/refactored behavior, not a defect, and provides enough scope for maintainers to act on it.