teos - Changes the behavior for updates of already triggered appointments

If an update for an already triggered appointment is received, it will be drop no matter if the locator is in the cache or not. This tries to prevent inconsistencies between the Watcher and the Responder, specially in the case of a reorg when data may have to flow backwards.
This commit is contained in:
Sergi Delgado Segura
2020-05-21 19:37:33 +02:00
parent 3228eeac6b
commit 708f2e1f3b
3 changed files with 8 additions and 9 deletions

View File

@@ -259,7 +259,6 @@ def test_add_appointment(watcher):
assert len(watcher.locator_uuid_map[appointment.locator]) == 2
# WIP: ADD appointment with the different uses of the cache
def test_add_appointment_in_cache(watcher):
# Generate an appointment and add the dispute txid to the cache
user_sk, user_pk = generate_keypair()