search

spacemeshos / smapp

Spacemesh App (Smesher + Wallet) 🏦📊
https://spacemesh.io
Apache License 2.0
128 stars 38 forks source link

Smapp displays NaN GiB data size on Smesher screen #1538

Open brusherru opened 11 months ago

brusherru commented 11 months ago

Environment

Describe the bug

Smapp displays Data Size: NaN GiB on the Smesher screen.

image

Steps to reproduce

  1. Run Smapp (smeshing should be already set up)
  2. Wait for Smapp to connect to Node
  3. Go to the Smesher screen

Expected behavior

It should display the actual PoS size

Actual behavior

It displays NaN GiB instead

monikasmolarek commented 11 months ago

@maparr After multiple attempts, I still could not reproduce it. The user that reported it initially confirmed on Discord that it disappeared for him as well by itself after some time.

monikasmolarek commented 11 months ago

Another User reported it, Sentry report ID aaf4ce744f69481182eae00d950dec4c

lrettig commented 11 months ago

another report: https://discord.com/channels/623195163510046732/981144592403537930/1163863347423363122

maparr commented 10 months ago

I wanted to share my thoughts on this particular issue. During the database compaction process introduced in go-spacemesh, there were instances where the node failed to respond correctly and provided inaccurate responses to smapp requests. Alternatively, it's possible that smapp had trouble interpreting the response correctly.

This problem was temporary and only affected users while they were compacting their databases, requiring them to wait for 4-24 hours for the process to complete.

While this issue bears some resemblance to issue 1474, it is a distinct problem.

In conclusion, this was a brief issue that primarily occurred when users had large state database sizes. Currently, the community is no longer experiencing this problem.

It's worth noting that we may encounter issues in any part of the system if it behaves differently from previous versions, such as longer response times from the node or the node waiting for certain conditions.

However, I haven't been able to reproduce this issue properly when my database state is not big, and the community hasn't reported the problem lately. In my opinion, we are in an acceptable state. Even if we were to attempt a fix, it would lack proper testing, which I strongly discourage.

cc: @lrettig , @brusherru , @monikasmolarek

poszu commented 5 months ago

@brusherru I have a similar problem but on the POS setup page: image