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

Feature: check redis when init #336

Closed
2 tasks done
AndrewZuo01 opened this issue Dec 22, 2023 · 3 comments
Closed
2 tasks done

Feature: check redis when init #336

AndrewZuo01 opened this issue Dec 22, 2023 · 3 comments
Labels
feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@AndrewZuo01
Copy link
Contributor

Checklist

  • I've searched for similar issues and couldn't find anything matching
  • I've discussed this feature request in the OpenIMSDK Slack and got positive feedback

Is this feature request related to a problem?

❎ No

Problem Description

now missing some check when chat start

Solution Description

check redis

Benefits

more thorough check

Potential Drawbacks

No response

Additional Information

No response
@AndrewZuo01 AndrewZuo01 added the feature Categorizes issue or PR as related to a new feature. label Dec 22, 2023
@cubxxw
Copy link
Contributor

cubxxw commented Dec 25, 2023

Could you please provide an update on whether there is a PR in progress for this issue? Additionally, could you kindly describe the approach for implementing the pre-launch check for the chat feature? Thank you.

@kubbot
Copy link
Contributor

kubbot commented Feb 24, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 24, 2024
@kubbot
Copy link
Contributor

kubbot commented Mar 2, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AndrewZuo01 @cubxxw @kubbot