Skip to content

bridgev2/portal: fix stale room capability state - #541

Open
Fizzadar wants to merge 1 commit into
mainfrom
nick/fix-stale-room-capabilities
Open

bridgev2/portal: fix stale room capability state#541
Fizzadar wants to merge 1 commit into
mainfrom
nick/fix-stale-room-capabilities

Conversation

@Fizzadar

@Fizzadar Fizzadar commented Aug 4, 2026

Copy link
Copy Markdown
Member

Capabilities were computed before ExtraUpdates applied the connector's freshly synced chat metadata, so the published capability set was always one metadata change behind, and the 24h throttle then dropped the correction entirely rather than deferring it.

  • move the UpdateCapabilities call in UpdateInfo to after ExtraUpdates
  • remove the 24h throttle, as the capability ID comparison already prevents redundant state events, and getting them is cheap

Capabilities were computed before ExtraUpdates applied the connector's freshly synced chat metadata, so the published capability set was always one metadata change behind, and the 24h throttle then dropped the correction entirely rather than deferring it.

Move the UpdateCapabilities call in UpdateInfo to after ExtraUpdates.
Remove the 24h throttle, as the capability ID comparison already prevents redundant state events.

@tulir tulir left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants