Steve Myers

I was able to get all the tests to pass except `test_sync_reorg_block()` for `electrum` by removing calls to `block_headers_subscribe()`, which now also returns the first header update, which is why...

I made a little more progress today, but still not clear on a proper fix. What I found is that in the `rust-electrum-client` crate, in the `raw_client::_reader_thread(..)` function there's a...

> > block_headers_subscribe(), which now also returns the first header update, which is why the block_headers_pop() never returns a value (it was already returned on subscribe). > > Are you...

The way the `test_sync_reorg_block()` currently works is it invalidates a block via bitcoind, then does a `block_headers_subscribe` and then polls in a loop on `block_headers_pop`. In this test we don't...

I was able to fix the `blockchain_tests` `wait_for_block()` loop this way: ```rust fn wait_for_block(&mut self, min_height: usize) { let mut header = self.electrsd.client.block_headers_subscribe().unwrap(); loop { if header.height >= min_height {...

I suspect there may be more wrong with `electrs` that could be related to what we're seeing with `get_history`. I manually started up in regtest mode `bitcoind 0.22`, `electrs 0.9.7`...

see comments in #724

I also have a PR that I think is a good way to fix this issue, but I need to dust it off and get some more discussion on it....

If you just need to use the latest pre-released version then the patch method is a good way to go. But to use it you also need to specify the...

In chat with @LLFourn sounds like this will also be of use to his projects. I propose: 1. After we create a new `release/0.x.0` branch we bump the version in...