Endpoint /transactions/addresses is not returning existing transactions

[brunodb3]

On testnet (could be happening on mainnet too), the /transactions/addresses endpoint is not returning what it should, leading to wrong behavior in the web wallet.

• https://testnet.lto.network/transactions/info/EFqPrYPQ9hBuv6WvcxThxBVb7vZq7UTAFXFphtHp7HBg
• http://testnet.lto.network/index/transactions/addresses/3N2kmoXi5SS54HrY3STaKGPA9TQ7KVKVMnV?type=anchor

The transaction exists on the chain, but the web wallet doesn't display it because of the wrong return of the endpoint.

This potentially has something to do with environment variables. TRANSACTION_INDEXING defaulting to false could mean that /transactions/addresses won't work properly, as it relies on the nodeService.countTransactionsByAddress() method.

If true, the docker-compose on the node repositories should be updated to include TRANSACTION_INDEXING=true.

[brunodb3]

After some investigation, I found that the issue is not related to environment variables, but with some synchronization issue with the listener services. If both anchor-listener and transaction-listener are turned on for example, the anchor-listener kicks in before transaction-listener finishes it's execution, preventing the data to be saved on database.

Further investigation is needed to figure out why this is happening and how to prevent it. But with this, we know for sure that this is also not working properly on mainnet.