element-hq / element-hq/dendrite

Hitting /profile after receiving a membership event races

Open
#1,489 3 comments 0 reactions 0 assignees View on GitHub
C-Client-API T-Defect X-Needs-Info
Dominant language
Go
Stars
965
Forks
101
PR merge metrics
No merged PRs in 30d

Description

*This issue was originally created by [**@ara4n**](https://github.com/ara4n) at .*

similar to https://github.com/vector-im/element-web/issues/8570, but @turt2live thinks it might be a race between /sync and /profile or something

Contributor guide

Open the contributing guide

Research direction

Start by comparing the reported /profile request with the /sync flow after a membership event, using the related Element issue 8570 as context. Confirm whether the failure is a race between those endpoints and trace the relevant Dendrite handlers. Done means the race is reproduced, its cause is identified, and /profile behaves correctly after the event.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.