chore: investigate transaction frozen issue on quick bot stop #9969
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
Investigating the issue of the transaction being frozen on quickly stopping the bot (if the contract is still open but we stopped the bot). For the solution, we are registering to the onMessage listener and listening for proposal open contracts (POC). If there is any POC that is triggered from the Bot project then wait for it first close then update the contract in UI so the transaction panel doesn't get stuck.
In the useEffect we are unsubscribing from the listener if the user moves away from the Bot project and again listens for it when they land on the Bot project. If it's subscribed once we are disabling it to subscribe again using a flag.