x42protocol / xCore

x42 wallet and running distributed applications
MIT License
11 stars 7 forks source link

Transaction Dashboard and Staking summary not auto refreshing #85

Closed mossboss007 closed 3 years ago

mossboss007 commented 3 years ago

Bug Description: in the past the transaction dashboard would auto refresh when a new transaction hit your wallet. This doesn't seem to be occurring anymore since the transaction history update.

In order to see new transactions i have to open transaction history. at that point the history updates and i can go back to the dashboard and see the updated transactions list.

Also after a day or two of the client being opened on the Dashboard screen, when i try to open the transaction history to force the dashboard to update it doesn't load the history for a long time, like 10 minutes maybe(i haven't timed it). and if i try to go back to dashboard it doesn't load. even if I let it sit for 5 minutes or longer it still doesn't load anything on the dashboard or transaction history I have to close the client and re launch to get it to work smoothly again.

I also noticed that the staking overview has the same issue. its not auto refreshing.

i do have a screen saver that turns on, i wonder if that is causing a problem for the refresh. i will try to turn screen saver off to see if that changes the behavior. Update: turning off Screen Saver had no effect. still not refreshing.

Steps to reproduce the bug:

  1. Go to the dashboard and note your last stake.
  2. let the client sit open for a while until you think you should have gotten another stake. you can open the log file and search for "Found new POS block hash" in the logs to see when your latest block was found.
  3. notice that the dashboard is not showing the latest stake transaction
  4. click on history to load the transaction history. this will force it to refresh. go back to dashboard and you will now see the latest transaction.

To reproduce the UI performance issue:

  1. open the client and start Hot staking
  2. leave the client open with the Dashboard displayed
  3. leave the client on for a day or more (depending on how quickly you are getting stake.) you will want it to stake at least 51 transactions (thinking of the 50 transaction max per page maybe)
  4. you will notice after a day or so that your dashboard is stale and not showing the most recent stakes.
  5. click on the history button to load the transaction history. this will take a long time. i'm not sure how long. i let it sit for about 3 minutes and it still hadn't loaded. i then walked away with it still trying to load and came back about 2 hours later and it had loaded at some point while i was gone. then try to go back to the dashboard. the dashboard will not load in a reasonable amount of time. i've let it sit for over 10 mins and it didn't load. try to go to the cold staking screen. it will not load either. go back to the dashboard, it still will not load. even your profile name will not load or will be very slow to load.
  6. to fix exit the client and relaunch it. performance will be back to normal.
  7. NOTE: if you leave the client open on the transaction history screen for more than a day you will not see this performance issue.

Screenshots: this screen shot was taken on 9/28 around 15:20 UTC. you can see the last stake it is showing is from 9/27 7:55pm (9/28 1:55am UTC) image

you can see in my log file i have a more current stake from 9/28 14:06 UTC image

Expected Behavior: dashboard should be auto refreshing. Also Staking summary should be auto refreshing if left in the tab where it is at today. others have suggested to move the staking summary to the Wallet drop down menu then it doesn't need to auto refresh. it would just be an on demand data retrieval. that would be a good solution as well. but either way the dashboard refreshing still needs to be addressed. could look like this: image

Desktop (please complete the following information if applicable): OS: win 10 Browser: Browser Version:

Additional Context: Add any other context, descriptions or information about the problem here.

Gabriel-x42 commented 3 years ago

Issue resolved! Thank you @mossboss007!