diff options
| author | Adam Soltys <[email protected]> | 2026-05-21 07:35:42 -0700 |
|---|---|---|
| committer | Adam Soltys <[email protected]> | 2026-05-21 07:35:42 -0700 |
| commit | cb0f1962238534ce0fa2261373a018bf34a868f5 (patch) | |
| tree | 6fe517ec0a2a96355129d3c8bcbe5cbd33a597bb /docker/arkd.Dockerfile | |
| parent | fe767002dd59f000d54fd09c9d617d69b9a5c894 (diff) | |
| download | coinos-server-cb0f1962238534ce0fa2261373a018bf34a868f5.tar.gz coinos-server-cb0f1962238534ce0fa2261373a018bf34a868f5.zip | |
sendLightning: silence success-case xpay log, re-read db before leak guard
Two cleanups based on a day of production data:
1. Only log the xpay response shape when something is abnormal
(failed_parts > 0 or missing preimage). The success case (200+/day) was
pure noise — answers Adam's "do we still need these xpay warnings".
2. Re-read the payment record from db before the leak guard fires. Several
"LEAKED DEBIT" lines today were finalize() throwing on a late line
(likely db.incrBy for the fee refund) AFTER db.set had already
persisted p.ref. The payment is functionally settled in those cases —
only flag as a real leak if ref is genuinely missing from the db record.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Diffstat (limited to 'docker/arkd.Dockerfile')
0 files changed, 0 insertions, 0 deletions