1d026d9b2b
When creating multiple streams using "POST /users/me/subscriptions" endpoint, same anonymous group was being used for settings of all the streams, like if can_subscribe_group was being set to an anonymous group, all streams created using that endpoint would use the same anonymous group for can_subscribe_group setting. Using the same anonymous groups for multiple streams caused unintended behavior - - Changing a setting for one stream also changed it for all other streams sharing the the same anonymous group, because eventually the members and subgroups of the group were updated. - Changing the setting to a named user group failed because `do_change_stream_permission_group` attempts to delete the anonymous group during the update. However, deletion of anonymous group is restricted if they are still referenced by setting fields. This commit fixes this so that one anonymous group is used only for one setting for a single stream. |
||
|---|---|---|
| .github | ||
| .vscode | ||
| analytics | ||
| api_docs | ||
| confirmation | ||
| corporate | ||
| docs | ||
| locale | ||
| patches | ||
| pgroonga | ||
| puppet | ||
| scripts | ||
| starlight_help | ||
| static | ||
| templates | ||
| tools | ||
| web | ||
| zerver | ||
| zilencer | ||
| zproject | ||
| .codecov.yml | ||
| .codespellignore | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlint | ||
| .mailmap | ||
| .npmignore | ||
| .prettierignore | ||
| .readthedocs.yaml | ||
| .sonarcloud.properties | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile-postgresql | ||
| eslint.config.js | ||
| LICENSE | ||
| manage.py | ||
| NOTICE | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| prettier.config.js | ||
| pyproject.toml | ||
| README.md | ||
| SECURITY.md | ||
| stylelint.config.js | ||
| tsconfig.json | ||
| uv.lock | ||
| Vagrantfile | ||
| version.py | ||
Zulip overview
Zulip is an open-source team collaboration tool with unique topic-based threading that combines the best of email and chat to make remote work productive and delightful. Fortune 500 companies, leading open source projects, and thousands of other organizations use Zulip every day. Zulip is the only modern team chat app that is designed for both live and asynchronous conversations.
Zulip is built by a distributed community of developers from all around the world, with 97+ people who have each contributed 100+ commits. With over 1,500 contributors merging over 500 commits a month, Zulip is the largest and fastest growing open source team chat project.
Come find us on the development community chat!
Getting started
-
Contributing code. Check out our guide for new contributors to get started. We have invested in making Zulip’s code highly readable, thoughtfully tested, and easy to modify. Beyond that, we have written an extraordinary 185K words of documentation for Zulip contributors.
-
Contributing non-code. Report an issue, translate Zulip into your language, or give us feedback. We'd love to hear from you, whether you've been using Zulip for years, or are just trying it out for the first time.
-
Checking Zulip out. The best way to see Zulip in action is to drop by the Zulip community server. We also recommend reading about Zulip's unique approach to organizing conversations.
-
Running a Zulip server. Self-host Zulip directly on Ubuntu or Debian Linux, in Docker, or with prebuilt images for Digital Ocean and Render. Learn more about self-hosting Zulip.
-
Using Zulip without setting up a server. Learn about Zulip Cloud hosting options. Zulip sponsors free Zulip Cloud Standard for hundreds of worthy organizations, including fellow open-source projects.
-
Participating in outreach programs like Google Summer of Code and Outreachy.
-
Supporting Zulip. Advocate for your organization to use Zulip, become a sponsor, write a review in the mobile app stores, or help others find Zulip.
You may also be interested in reading our blog, and following us on Twitter and LinkedIn.
Zulip is distributed under the Apache 2.0 license.