fix(knex): bump knex from 2.4.1 to 2.5.1 to resolve leaking db connections #3751
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
📸 Preview service has generated an image. |
iainsproat
changed the title
adamhathcock
approved these changes
Dec 31, 2024
fabis94
approved these changes
Jan 2, 2025
|
Deployed to |
iainsproat
deleted the
iain/web-1186-postgres-connections-in-objects-pod-should-not-be-leaked
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description & motivation
Knex
^2.5.0contains a fix for hanging connections when streams are prematurely closed: knex/knex#5243This may be the source of the resource leak of database connections.
The changelogs for knex do not indicate any breaking changes.
Changes:
To-do before merge:
Screenshots:
Validation of changes:
Checklist:
References