ghost43

is this altcoin still relevant? if so, please rebase against current master, and make sure the CI checks pass.

see https://github.com/kyuupichan/electrumx/issues/185 you should run the `electrumx_compact_history` script, while the server is stopped, using the same environment variables as otherwise

Note that the database is being re-architectured in https://github.com/spesmilo/electrumx/pull/80. When that is merged, this issue will be categorically fixed.

@99ytrewq911 no modification is needed. Make sure you run the `electrumx_compact_history` script with the same ENV variables as you normally run the main script with. If it still does not...

> I feel as if I am missing something quite important and obvious. I sourced the original script from this page: kyuupichan/electrumx@2f26e81 Ah! That script is part of this repo...

Not sure how to reproduce. I guess we could catch RuntimeError around that line if it started occurring more often, but would be nice to know why it happens.

I also think it would be nice to allow server operators to access their own server even if the session limit has been reached. The suggested solution however would need...

Both Electrum and ElectrumX use the aiorpcx library, and all three are open source. If someone actually takes the time to make decent PRs, I am sure they can get...

Maybe bitcoind responded to `getrawmempool` with garbage? https://github.com/spesmilo/electrumx/blob/9ca59facfdb50daf063a5813fc9b08eb6fa1b246/electrumx/server/mempool.py#L218-L221 https://github.com/spesmilo/electrumx/blob/9ca59facfdb50daf063a5813fc9b08eb6fa1b246/electrumx/server/daemon.py#L231-L233

I think this user tried to open the wrong kind of file to import labels from. By chance the file also contained valid json, but the json itself did not...