1098 sats \ 16 replies \ @Athena 16 Jul \ on: Stacker Saloon
https://m.stacker.news/39998
@k00b, @ek please look into this and suggest
write
preview
13 sats \ 15 replies \ @k00b 16 Jul
What were you trying to do?
reply
46 sats \ 14 replies \ @Athena 16 Jul
I just do one comment and zap. Then this reflects. Can't understand what is this for
reply
10 sats \ 13 replies \ @Bell_curve 16 Jul
This happens to me occasionally
Wait ten seconds and try zap ⚡️ again
reply
35 sats \ 4 replies \ @Athena 16 Jul
Ok . But why is this error shown?
reply
23 sats \ 1 reply \ @k00b 16 Jul
Because a database transaction is timing out.
reply
24 sats \ 0 replies \ @Athena 16 Jul
Ok got it. Thanks
reply
13 sats \ 1 reply \ @ek 16 Jul
Because it failed and we don't have user-friendly error messages yet.
Until we found out what's taking so long and fixed this, a retry should usually work.
reply
0 sats \ 0 replies \ @Bell_curve 16 Jul
I can testify that a retry works after waiting 5 seconds
reply
13 sats \ 1 reply \ @k00b 16 Jul
I've made some improvements around this. Please let us know if it continues happening. Thank you so much reporting!
reply
100 sats \ 0 replies \ @Bell_curve 16 Jul
No problem, thanks
reply
13 sats \ 5 replies \ @k00b 16 Jul
Is this from the custodial wallet?
reply
0 sats \ 4 replies \ @Bell_curve 16 Jul
Browser is duck duck go
Mobile is iOS
reply
13 sats \ 3 replies \ @k00b 16 Jul
Thanks. Are you zapping from the SN wallet or scanning a QR code?
reply
100 sats \ 2 replies \ @Bell_curve 16 Jul
Wallet
reply
13 sats \ 1 reply \ @k00b 16 Jul
Thanks. Is it just a single zap or many one sat zaps?
view replies