Closed jpaulet closed 5 months ago
These things are ui-components related (chakra-components to be more precise), transferring the issue there.
The toasts messages after modifying the process status (pause, play, etc.) don't disappear and get stacked. This happens at least on the org page.
Cannot reproduce neither on the org page or process page on develop branch
The toasts messages after modifying the process status (pause, play, etc.) don't disappear and get stacked. This happens at least on the org page.
Cannot reproduce neither on the org page or process page on develop branch
It can be reproduced if you close the dropdown menu while the action is loading. It's due to how the context and state is managed there, since I did some tricks when adding backwards compatibility.
I cannot reproduce it neither closing the dropdrown. After a while the toast disappear (when the transaction is succeeded)
Try in the org page, with multiple running processes, if you pause one, then another, then another, the toast don't disappear.
Missatge de selankon @.***> del dia dc., 3 d’abr. 2024 a les 12:38:
I cannot reproduce it neither closing the dropdrown. After a while the toast disappear (when the transaction is succeeded)
— Reply to this email directly, view it on GitHub https://github.com/vocdoni/ui-components/issues/153#issuecomment-2034208989, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUTF6K6JAEIU4SBVC66FDDY3PLZTAVCNFSM6AAAAABFTBNXNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZUGIYDQOJYHE . You are receiving this because you authored the thread.Message ID: @.***>
Ok I tried to break the program but impossible. It works to well
Pausing/Restarting this 4 elections, it won't break anything, and the toats goes after a while. The most strange thing i got is this error message
Ok I tried to break the program but impossible. It works to well
Weird, I remember this and I just tried and same. Cannot reproduce it anymore.
Pausing/Restarting this 4 elections, it won't break anything, and the toats goes after a while. The most strange thing i got is this error message
This is somehow "expected", since you tried to run multiple actions in parallel, the nonce wasn't properly updated and you triggered an action with a repeated nonce, causing the txn to fail.
Closing unless someone finds a current way to reproduce it.
After the PxLl voting process, we should solve & improve some issues: