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.

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

Track PooledConnection state explicitly #189

Merged
merged 5 commits into from
Feb 1, 2024
Merged

Track PooledConnection state explicitly #189

merged 5 commits into from
Feb 1, 2024

Conversation

djc
Copy link
Owner

@djc djc commented Feb 1, 2024

No description provided.

Copy link

codecov bot commented Feb 1, 2024

Codecov Report

Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (6ca2efc) 72.47% compared to head (90db001) 72.51%.

Files Patch % Lines
bb8/src/api.rs 58.33% 5 Missing ⚠️
bb8/src/inner.rs 90.90% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #189      +/-   ##
==========================================
+ Coverage   72.47%   72.51%   +0.04%     
==========================================
  Files           6        6              
  Lines         534      553      +19     
==========================================
+ Hits          387      401      +14     
- Misses        147      152       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

djc added 4 commits February 1, 2024 10:57
0dca340 caused a regression where the
library would update the pool state to mark a connection as lost because
we disconnected the underlying connection from the `PooledConnection`.
Instead, add a `state` field to `PooledConnection` that tracks the
state of the `conn` field, so we can do the right thing on drop.
@djc djc merged commit ed37efb into main Feb 1, 2024
10 checks passed
@delete-merged-branch delete-merged-branch bot deleted the track-state branch February 1, 2024 10:03
@djc
Copy link
Owner Author

djc commented Feb 1, 2024

Merged and published this proactively to make this easy to consume and since I'm pretty sure it addresses a regression from 0.8.2. Still happy to address any feedback anyone might have!

nicolasvan added a commit to OneSignal/pgcat that referenced this pull request Mar 12, 2024
nicolasvan added a commit to OneSignal/pgcat that referenced this pull request Mar 18, 2024
To get djc/bb8#186 and djc/bb8#189
which fix potential deadlocks (djc/bb8#154)
magec pushed a commit to OneSignal/pgcat that referenced this pull request Oct 23, 2024
To get djc/bb8#186 and djc/bb8#189
which fix potential deadlocks (djc/bb8#154)
magec pushed a commit to OneSignal/pgcat that referenced this pull request Oct 23, 2024
To get djc/bb8#186 and djc/bb8#189
which fix potential deadlocks (djc/bb8#154).

Also, this (djc/bb8#225) was needed to prevent a connection
leak which was conveniently spotted in our integration tests.
drdrsh pushed a commit to postgresml/pgcat that referenced this pull request Oct 28, 2024
* Update bb8 to 0.8.6

To get djc/bb8#186 and djc/bb8#189
which fix potential deadlocks (djc/bb8#154).

Also, this (djc/bb8#225) was needed to prevent a connection
leak which was conveniently spotted in our integration tests.

* Ignore ./.bundle (created by dev console)

---------

Co-authored-by: Jose Fernandez (magec) <joseferper@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant