30b7814aaf
scheduler()'s defer unconditionally calls close(b.data). If the channel
was closed by the caller (or an upstream producer) instead of via the
normal Close()-sends-nil path, the receive on b.data returns ok == false,
scheduler returns, and the deferred close(b.data) then fires on an
already-closed channel:
panic: close of closed channel
reliably reproducible under the #3653 steps (manually closing b.data
while Start() is running).
Track whether we observed the external-close via a local
`externallyClosed` flag set in the `ok == false` branch. The defer
only closes b.data when that flag is false, i.e. when the scheduler
exited through the nil-message or ticker paths and still owns the
channel. No behaviour change on the graceful Close() path.
Fixes #3653
English · 中文 · Українська · Česky · Magyar · Español · فارسی · Français · Deutsch · Polski · Indonesian · Suomi · മലയാളം · 日本語 · Nederlands · Italiano · Русский · Português (Brasil) · Esperanto · 한국어 · العربي · Tiếng Việt · Dansk · Ελληνικά · Türkçe
👥 Join Our Community
Ⓜ️ About OpenIM
Unlike standalone chat applications such as Telegram, Signal, and Rocket.Chat, OpenIM offers an open-source instant messaging solution designed specifically for developers rather than as a directly installable standalone chat app. Comprising OpenIM SDK and OpenIM Server, it provides developers with a complete set of tools and services to integrate instant messaging functions into their applications, including message sending and receiving, user management, and group management. Overall, OpenIM aims to provide developers with the necessary tools and framework to implement efficient instant messaging solutions in their applications.
🚀 Introduction to OpenIMSDK
OpenIMSDK, designed for OpenIMServer, is an IM SDK created specifically for integration into client applications. It supports various functionalities and modules:
-
🌟 Main Features:
- 📦 Local Storage
- 🔔 Listener Callbacks
- 🛡️ API Wrapping
- 🌐 Connection Management
-
📚 Main Modules:
- 🚀 Initialization and Login
- 👤 User Management
- 👫 Friends Management
- 🤖 Group Functions
- 💬 Session Handling
Built with Golang and supports cross-platform deployment to ensure a consistent integration experience across all platforms.
🌐 Introduction to OpenIMServer
- OpenIMServer features include:
- 🌐 Microservices Architecture: Supports cluster mode, including a gateway and multiple rpc services.
- 🚀 Diverse Deployment Options: Supports source code, Kubernetes, or Docker deployment.
- Massive User Support: Supports large-scale groups with hundreds of thousands, millions of users, and billions of messages.
Enhanced Business Functions:
-
REST API: Provides a REST API for business systems to enhance functionality, such as group creation and message pushing through backend interfaces.
-
Webhooks: Expands business forms through callbacks, sending requests to business servers before or after certain events.
🚀 Quick Start
Experience online for iOS/Android/H5/PC/Web:
To facilitate user experience, we offer various deployment solutions. You can choose your preferred deployment method from the list below:
System Support
Supports Linux, Windows, Mac systems, and ARM and AMD CPU architectures.
🔗 Links
✍️ How to Contribute
We welcome contributions of any kind! Please make sure to read our Contributor Documentation before submitting a Pull Request.
Thank you for contributing to building a powerful instant messaging solution!
📕 License
This software is licensed under the Apache License 2.0