Electrs not indexing unconfirmed transactions as spent

[softsimon]

We're seeing this on multiple (but not all) servers in production.

A transaction in the mempool https://node205.tk7.mempool.space/api/tx/b60793ec024f9425d8d7841d592adc8782b3d32921d0ce5a7e894bd62e00973c spending an input f7f8befc733c643f7455744d82e665a9c7dcc6fb37f1c0aa56862340aa0e698b is not registered in the address transactions API and shows up as unspent in the Outspends API endpoint https://node205.tk7.mempool.space/api/tx/f7f8befc733c643f7455744d82e665a9c7dcc6fb37f1c0aa56862340aa0e698b/outspend/344

{"spent":false}

Version mempool-electrs 3.0.0-dev-3c66022

On another server with the exact same githash, it does work https://node206.tk7.mempool.space/api/tx/f7f8befc733c643f7455744d82e665a9c7dcc6fb37f1c0aa56862340aa0e698b/outspend/344

{"spent":true,"txid":"b60793ec024f9425d8d7841d592adc8782b3d32921d0ce5a7e894bd62e00973c","vin":0,"status":{"confirmed":false}}

[junderw]

Subtitle:
P2P bugs are fun.

If the git hash is the same, the only difference would be the order in which the unconfirmed transactions arrived. Confirmed transactions probably won't have any issues.

Trying to consolidate a bunch of mempools into one global mempool state is hard stuff.

I think #25 fixes this issue... But we need further testing.

[junderw]

It's been about a month since #25 was merged.... has this issue re-appeared at all?