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

I did a thread and it went wrong for Travis (maybe other folks too?) #23249

Closed
lampholder opened this issue Sep 9, 2022 · 4 comments
Closed

I did a thread and it went wrong for Travis (maybe other folks too?) #23249

lampholder opened this issue Sep 9, 2022 · 4 comments
Labels
A-Threads O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@lampholder
Copy link
Member

Steps to reproduce

  1. Where are you starting? What can you see?
    I made a thread and typed lots of messages in it

Outcome

The thread looked good for me, but for Travis it looked like a giant pile of replies.

Operating system

Windows 10

Application version

Element Nightly version: 0.0.1-nightly.2022090801 Olm version: 3.2.12

How did you install the app?

website

Homeserver

lant.uk

Will you send logs?

Yes
@duxovni duxovni added S-Minor Impairs non-critical functionality or suitable workarounds exist O-Uncommon Most users are unlikely to come across this or unexpected workflow A-Threads labels Sep 9, 2022
@robintown
Copy link
Member

I'm pretty sure Travis has the threads beta disabled, and is looking at the fallbacks?

@robintown
Copy link
Member

@turt2live Could you confirm?

@turt2live
Copy link
Member

yes, this is the fallbacks. The sending client appeared to use the thread root as the fallback for every message, which made the history unusable.

@t3chguy
Copy link
Member

t3chguy commented Sep 12, 2022

Duplicate of #23147

@t3chguy t3chguy marked this as a duplicate of #23147 Sep 12, 2022
@t3chguy t3chguy closed this as completed Sep 12, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Threads O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@turt2live @lampholder @t3chguy @duxovni @robintown