-
-
Notifications
You must be signed in to change notification settings - Fork 111
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.
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
add pool for pubsub connections #159
Conversation
redis/src/lib.rs
Outdated
} | ||
|
||
async fn is_valid(&self, _conn: &mut Self::Connection) -> Result<(), Self::Error> { | ||
// TODO: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something needs to be done here, but not sure what would be best for a PubSub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe punsubscribe()
with an empty pattern?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea. Made that change, just trying to validate a few things.
Ok, pushed the logic for |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #159 +/- ##
==========================================
- Coverage 74.28% 72.45% -1.83%
==========================================
Files 6 6
Lines 556 570 +14
==========================================
Hits 413 413
- Misses 143 157 +14
☔ View full report in Codecov by Sentry. |
I mean, if you can't validate this stuff, why are we considering this for inclusion? |
Well, the basic functionality (retrieving a connection) does work, it's the
So was merely trying to defer to you on how you wanted to move forward. |
Even though we have no tests, given that the entire idea of using |
Sorry for the lack of follow-up here...we ended up going in a different direction (no longer using redis due to other reasons), so I likely won't have time to come back to this. |
No problem, thanks for following up! I'll close this -- if someone else wants it, please submit a new PR. |
Based on discussion in #70