Test plan

1. in the Admin Console
   1. if the Semaphores database table isn't empty, then clear it
   2. go to the Configuration → Website → Advanced section
   3. confirm, that the Delete Stuck Semaphores after system setting is present
   4. go to Configuration → Website → Stop Words section
   5. open any record for editing
   6. save it
   7. confirm, that the Semaphores table is still empty
2. in IDE:
   1. open \kTempTablesHandler::SaveEdit method for editing
   2. comment-out the code, that deletes a semaphore (between $ids = $this->DoCopyTempToOriginal($this->Tables, null, $master_ids); and return $ids;
   3. save changes
3. in the Admin Console
   1. go to Configuration → Website → Stop Words section
   2. open any record for editing
   3. save it
   4. confirm, that the Semaphores table has 1 record now related to the edited record
   5. go to the Configuration → Website → Scheduled Tasks section
   6. run the delete_stuck_semaphores scheduled task
   7. confirm, that above added semaphore record is still present in the Semaphores table
   8. go to Configuration → Website → Stop Words section
   9. open same record for editing and try to save it
   10. confirm, that:
       • after a delay of 30 seconds you'll see an alert explaining that saving has failed
       • the record was added to the Logs & Reports → System Logs section about a parallel editing attempt
   11. subtract 305 from the Timestamp column value of the above-added semaphore record (+save changes to db)
   12. run the delete_stuck_semaphores scheduled task
   13. confirm, that:
       • the above-added semaphore record is removed from the Semaphores table
       • the record was added to the Logs & Reports → System Logs section about a detected stuck semaphore