You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
loop/loopdb/sqlc
Andras Banki-Horvath 6a4ef3683a
sweepbatcher: fix spawning condition "unattached" spend notifiers
Previously, when handling a sweep we assumed that if a sweep status
was completed, the parent batch was also finished. However, since the
batch confirmation status depends on three on-chain confirmations, it
is possible that a spend notifier was started for a sweep of an active
batch. The notifier would fetch the parent batch from the database, but
because we incorrectly assumed that  the parent was confirmed (when it
was not), the DB call would fail with a 'no rows returned' error.
This failure would cause the sweep to fail and the sweep batcher to
stop, resulting in a permanent failure state.
2 months ago
..
migrations
queries sweepbatcher: fix spawning condition "unattached" spend notifiers 2 months ago
batch.sql.go sweepbatcher: fix spawning condition "unattached" spend notifiers 2 months ago
db.go
instantout.sql.go
liquidity_params.sql.go
migration_tracker.sql.go
models.go
querier.go
reservations.sql.go
swaps.sql.go