atlas
atlas copied to clipboard
Joystream
Wait for other transaction
From time to time, I get this dialogue when I try to do a transaction
In this case, I had not used Gleev for many hours, so there could not really be an question about some sort of real conflict.
Do we know what would be the likely cause of this in such a scenario? Please write in response below.
After a bit of waiting, and a few attempts, it finally just worked, for unknown reasons, but had to try many times.
After a bit of waiting, and a few attempts, it finally just worked, for unknown reasons, but had to try many times.
What we can introduce is a more sophisticated way to block related transactions ( we would have to identify which txs shouldn't be launched one after another without confirmation). It would be good to have some place where we could inspect transactions that are in progress.
What we can introduce is a more sophisticated way to block related transactions ( we would have to identify which txs shouldn't be launched one after another without confirmation). It would be good to have some place where we could inspect transactions that are in progress.
The moment we start to do this, we really have to consider managing transaction life-cycle on the server-side, because multiple tabs or browsers will not respect such logic if its client side. I guess we can start trying this on client side, but only makes sense if its not a huge undertaking.
Discussed. This is a huge undertaking. Sending back to backlog for now.
Which part is huge? client side? server-side? something else?
Proper client + server solution.
For now, we can just remove transaction blocking in general, I cannot think of any drawbacks.