matrix-org / matrix-org/matrix-hookshot
Display names resetting on upgrade/redeployment?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 450
- Forks
- 95
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 23
Description
Is it expected behavior that when I stop and destroy my matrix-hookshot compose stack and redeploy it, or when it's upgraded, the display names of the created webhooks reset? I had the display names changed via synapse-admin, before they reset.
This only affects display names not avatar images, and only webhooks created via the setup widget, not the ones created via the .!hookshot command
EDIT1: Upon further inspection, it seems the newly introduced Static Connections might be needed to configure in order to prevent webhook display name reset, which imo isn't so clear. Can it be used for existing webhooks? Or is it totally unrelated?
EDIT2: Seems to be fixed after (correctly) re-configuring docker postgres_data volume binding for synapse and mas' database, in newer postgres v18. Which I assume was the cause of display names not persisting. But will monitor the situation a bit further.
So it's most likely fixed now and my issue probably wasn't even related to a matrix-hookshot update.
EDIT3: It unfortunately doesn't seem to be fixed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/usage/static_connections.md and the setup widget flow, then reproduce an upgrade or redeployment with the reported Docker and PostgreSQL volume setup. Check whether webhook display names persist while avatar images remain intact, and document whether Static Connections applies to existing webhooks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100