Closed bautisflow closed 1 year ago
Describe the bug When a sync with locks is erases, and the a new sync is created with the same id as the one deleted, locks are still available.
To Reproduce Steps to reproduce the behavior:
curl -XPOST -H "Content-Type: application/json;charset=UTF-8" -H 'Authorization: Bearer <token>' 'https://perf.aws.thinger.io/v1/users/bautisflow/syncs/test_sync/locks' -d '{"lock":"caracola1","slots":1,"timeout":0}' | jq
Expected behavior Locks should be deleted from database
Additional context If the locks are maintained other services (database scraper) would return confusing information.
Describe the bug When a sync with locks is erases, and the a new sync is created with the same id as the one deleted, locks are still available.
To Reproduce Steps to reproduce the behavior:
Expected behavior Locks should be deleted from database
Additional context If the locks are maintained other services (database scraper) would return confusing information.