Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sent message (but not synced) stays at bottom of timeline #1192

Closed
BillCarsonFr opened this issue Apr 1, 2020 · 8 comments
Closed

Sent message (but not synced) stays at bottom of timeline #1192

BillCarsonFr opened this issue Apr 1, 2020 · 8 comments
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems X-Needs-Investigation

Comments

@BillCarsonFr
Copy link
Member

Looks like there has been an issue with a message that was sent correctly but never synced back by the server (something that should not happen :/)

The issue is that riotX is putting the message in it's final position in the timeline when the remote echo is received back from the server.

Notice that in this case, other sessions for that user do not see the message..
@BillCarsonFr BillCarsonFr added T-Defect Something isn't working: bugs, crashes, hangs and other reported problems X-Needs-Investigation labels Apr 1, 2020
@BillCarsonFr BillCarsonFr changed the title Sent message stays at bottom of timeline Sent message (but not synced) stays at bottom of timeline Apr 1, 2020
@selfisekai
Copy link

can reproduce easily because of my bad homeserver media storage. in this case it returned HTTP 500 error on sending. note the date - messages above were sent on 2020-04-05.
Screenshot_20200405-232830_RiotX_dbg
Screenshot_20200405-232838_RiotX_dbg

@BillCarsonFr
Copy link
Member Author

See matrix-org/synapse#7206

@BillCarsonFr
Copy link
Member Author

BillCarsonFr commented Apr 8, 2020 •
edited
Loading

can reproduce easily because of my bad homeserver media storage. in this case it returned HTTP 500 error on sending. note the date - messages above were sent on 2020-04-05.
....

I think it's something else .on what riotX version are you?

@selfisekai
Copy link

selfisekai commented Apr 8, 2020 •
edited
Loading

can reproduce easily because of my bad homeserver media storage. in this case it returned HTTP 500 error on sending. note the date - messages above were sent on 2020-04-05.
....

I think it's something else .on what riotX version are you?

0.19.0-dev from https://fdroid.krombel.de/riotx-dev-gplay/fdroid/repo (buildkite build copies) currently, the image sending attempt was probably made from an older version though. the media uploading issues persist for all homeserver users on all devices clients we tried (Riot.im/RiotX for Android, Riot.im Desktop and browser). it's hosted on a raspberry pi with min.io, over a 10 Mb/s upload connection, tunneled via ssh and mounted to a directory with goofys. so yes, this may cause problems.
the thing is, when I use for example Riot.im Desktop, file upload just gets rejected and nothing happens. but on RiotX it just stays forever at the end of my chat history.

@fbruetting
Copy link

Duplicate of #516 ?

@bjonnh
Copy link

bjonnh commented Dec 27, 2020

We have a few recent reports #2582 #2494 #2358 of that as well.

This is still happening on the latest Fdroid version (english phone and settings) default matrix/vector server.

@Totogro Totogro mentioned this issue Dec 31, 2020
Closed
@Krzmbrzl
Copy link

Possible workaround: #2358 (comment)

@richvdh
Copy link
Member

richvdh commented Aug 27, 2021

I'm going to close this as a dup of #516.

@richvdh richvdh closed this as completed Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems X-Needs-Investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@bjonnh @richvdh @BillCarsonFr @fbruetting @selfisekai @Krzmbrzl