Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG]Using the client's time for sending messages in OpenIM is not advisable; it is recommended to use the server's time instead #786

Open
xintai777 opened this issue Jul 3, 2024 · 1 comment
Open

[BUG]Using the client's time for sending messages in OpenIM is not advisable; it is recommended to use the server's time instead #786

xintai777 opened this issue Jul 3, 2024 · 1 comment
Assignees
@mo3et
Labels
planning

Comments

@xintai777
Copy link

OpenIM Server Version

3.7.0

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Source Code Deployment

Bug Description and Steps to Reproduce

Using the client's time for sending messages in OpenIM is not advisable; it is recommended to use the server's time instead.

Screenshots Link

No response
@xintai777 xintai777 added the bug Categorizes issue or PR as related to a bug. label Jul 3, 2024
@kubbot kubbot changed the title [BUG] [BUG] Jul 3, 2024
@kubbot
Copy link
Contributor

kubbot commented Jul 3, 2024

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

@skiffer-git skiffer-git changed the title [BUG] [BUG]Using the client's time for sending messages in OpenIM is not advisable; it is recommended to use the server's time instead Sep 27, 2024
@FGadvancer FGadvancer transferred this issue from openimsdk/open-im-server Nov 21, 2024
@skiffer-git skiffer-git added planning and removed bug Categorizes issue or PR as related to a bug. labels Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mo3et mo3et

Labels
planning
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@xintai777 @mo3et @skiffer-git @kubbot