Jörg Maier
Jörg Maier
Any news on this topic ? @sideninja
@bluesign short question, I do not understand your last comment. Does the pull request solve both problems or only one of the problems ?
@sideninja this issue is not resolved. See for example transaction: e8a51280ae3a3df06263ac5ddb8239f8bb7ae76ed37f59865aa9aa5fa42d83c2 flow transactions get e8a51280ae3a3df06263ac5ddb8239f8bb7ae76ed37f59865aa9aa5fa42d83c2 -n mainnet -o json This doesn't return. I understood also that @bluesign addressed this issue...
@sideninja: Actually no. See for example the transaction fd561db7293c156f702617fce43876409c4b44f83c1de5d89008962fd0d30de3 this one is from September. In the past the client did work for all transactions no matter if a spork happened...
@sideninja thank you.
@sideninja thanks for the tip. I was looking into this too. But the content between the client and the REST API is very different. Actually the events and what happened...
@sideninja can you deploy a new version ?