gnosis / gnosis/safe-cmm-app-react

Bug: Strategy doesn't refresh after requesting withdraw

Open
#174 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

# Description
Strategy doesn't refresh after requesting withdraw

# To Reproduce:
Steps to reproduce the behavior:
1. Deploy one strategy
1. Wait a few minutes for it to be available (~5min)
1. Go to Strategies > Active
1. Expand the new Strategy by clicking on the row/down arrow
1. Click on `Request Withdraw`
1. Confirm, send the tx and make sure all signers approve/execute it.
1. Wait on the same page for 5 min

# Expected Behaviour
The strategy is removed from Active and moved to Closed

# Actual Behaviour
Strategy remains where it is

# Screenshots/Videos
Strategy is stuck on this state:
![screenshot_2020-11-27_10-06-57](https://user-images.githubusercontent.com/43217/100475531-335fa300-3098-11eb-81ca-467ce98a09e3.png)

# Environment
**Desktop:**
- OS: Linux
- Browser FF
- Version 0.4.0 - development - 204904665 - 43ce03

# Background

Same thing can be said for Closed strategies. After claiming, the UI is never updated to indicate that:
![screenshot_2020-11-27_10-12-51](https://user-images.githubusercontent.com/43217/100475952-3c04a900-3099-11eb-86da-01ad10b0e6e3.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in the Strategies > Active flow and reproduce a completed Request Withdraw transaction with all signers approving it. Compare the Active and Closed views, including the claiming case, and verify that the strategy moves or updates on the same page after the expected wait.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.