Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Parity never loads the transaction history, not any past transaction detail shown #6853

Closed
zumbatan opened this issue Oct 22, 2017 · 10 comments
Labels
F2-bug 🐞 The client fails to follow expected behavior. P5-sometimesoon 🌲 Issue is worth doing soon.

Comments

@zumbatan
Copy link

zumbatan commented Oct 22, 2017

Before filing a new issue, please provide the following information.

I'm running:

    Parity version: 1.7.6
    Operating system: Windows
    And installed: via installer

Description::
Open the Accounts tab, click on your available Ethereum account

Expected result::
account information is displayed with full transaction history

Actual Bug::
There is not any past transaction information displayed, not any history. After opening an account, I see for c. 3seconds the "loading" symbol at the spot where the transaction history should be displayed. But the loading symbol always disappears after c. 3seconds without having loaded anything.

My wallet is always fully synched, open and active for many hours, longer than 1day, still never saw my transaction history!

Why is this essential account information missing, how can we fix so that all sent and received transactions are displayed properly?

Thank you very much for any solution

@zumbatan zumbatan changed the title Encountered issues with wallet transactions history not being displayed Parity never loads the transaction history, not any past transaction detail shown Oct 22, 2017
@Office-Julia Office-Julia added the Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. label Oct 22, 2017
@Office-Julia
Copy link
Contributor

Hello. Could you please share more details on this issue:
Parity Issue-Checklist

  1. Have you tried turning Parity client off and on again?
  2. Have you tried to upgrade to 1.7.7? It's Parity latest stable release version.
  3. Which version of Windows are you using now?
  4. What flags/params are you running Parity with?
  5. Do you use any specific config file?
  6. Please, share the exact error message if there is any or your logs
  7. Could you double check are you connected to any peers at the moment when problem occurs?
  8. What's your time? Is it synchronised to time.is ?

@Office-Julia Office-Julia added the F2-bug 🐞 The client fails to follow expected behavior. label Oct 22, 2017
@slothbag
Copy link

slothbag commented Oct 22, 2017

Could this be related to the broken filters? #6637

Not related

@zumbatan
Copy link
Author

@slothbag @Office-Julia
thanks for reply, here more details:

Have you tried turning Parity client off and on again? yes, often
Have you tried to upgrade to 1.7.7? It's Parity latest stable release version. - no (but shouldn't it also work with 1.76?) ->In my view this seems to be a global bug coming and going, because until now i have seen this issue on EVERY past version.

What flags/params are you running Parity with? -i am on ethereum foundation server
Do you use any specific config file? no
Please, share the exact error message if there is any or your logs. - there is not any error
Could you double check are you connected to any peers at the moment when problem occurs? - i am always connected to several peers
What's your time? Is it synchronised to time.is ?  my time is never synched (always about 50 to 500ms). but there is another open bug for this time synch issue, too, i guess.  But this should not be the trigger for the missing transaction historiy, right? because the tx history was displayed sometimes although time was not in sync.

I can imagine displaying the transation history should not be any issue, at the end it is just past, static data to be fetched/retrieved from etherscan. why is it strongly malfunctioning? Any ideas for the cause? Do you know of other users who observed this?

@zumbatan
Copy link
Author

zumbatan commented Oct 31, 2017

@Office-Julia @5chdn any idea yet to this big issue? why there are no transaction history displayed?

UPDATE: Issue still persisting for several days with newer v1.78 parity. Issue exists with newest chrome&firefox browsers. No addons or whatsoever. I am always fully synched. With v1.78 even the time is always synched. But still not any transaction history displayed.

thanks

@5chdn 5chdn added M7-ui P5-sometimesoon 🌲 Issue is worth doing soon. and removed Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Nov 2, 2017
@5chdn 5chdn added this to the 1.9 milestone Nov 2, 2017
@5chdn
Copy link
Contributor

5chdn commented Nov 2, 2017

Probably issues with Etherscan-API.

@5chdn 5chdn modified the milestone: 1.9 Dec 6, 2017
@a1654
Copy link

a1654 commented Jan 10, 2018

I'm having exact same issue; any solutions here?

@jacogr
Copy link
Contributor

jacogr commented Jan 17, 2018

The way it operates is that it gets the hashes from Etherscan and then tries to find the blocks on the local node. If these are pruned/not available, it won't display. (e.g. currently for me it only displays the txs made in the last 1k blocks)

Fixable by falling back to the Etherscan values when not in the local node - however would need to be done for 1.10 with applicable backports.

@jacogr jacogr modified the milestones: 1.9, 1.10 Jan 17, 2018
@5chdn 5chdn modified the milestones: 1.10, 1.11 Jan 23, 2018
@vveljk
Copy link

vveljk commented Jan 29, 2018

I have the same problem....some transactions are visible and some are not. Could it be possible that DB is partly corrupted? I also don't see any Altcoin and I could see them like week or two ago.
Is there any solution to recheck DB and fix it if needed? Or do I need to make full sync again in order to solve this issue?

@Eriksn1970
Copy link

I have the same issue: using version 1.7.8 and always could see my tokens, but since 2 days not anymore?
It's fully synced, time ok. What should I do?

@5chdn
Copy link
Contributor

5chdn commented Jan 31, 2018

Token balances will be fixed with 1.9.1 and 1.8.8 - apparently the token registry is too big right now this causes issues.

@5chdn 5chdn closed this as completed Jan 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. P5-sometimesoon 🌲 Issue is worth doing soon.
Projects
None yet
Development

No branches or pull requests

8 participants