-
Notifications
You must be signed in to change notification settings - Fork 37
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
Update shapeless to 2.3.10 #291
Open
scala-steward
wants to merge
15
commits into
finagle:master
Choose a base branch
from
scala-steward:update/shapeless-2.3.10
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update shapeless to 2.3.10 #291
scala-steward
wants to merge
15
commits into
finagle:master
from
scala-steward:update/shapeless-2.3.10
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
PostgreSQL prepared statements and portals are referenced by names, where setting an empty string is ok, as it means it is unnamed prepared statement. [1] However there is a weird issue happening under high loads where a different set of parameters are being set to the wrong prepared statements: `bind message supplies 10 parameters, but prepared statement “...” requires 12` And also sporadically we get `ERROR: portal "" cannot be run` making it super hard to troubleshoot as all portals currently share the same name. Setting a unique name for each prepared statement has fixed the problem in our production setting, however I am not able to pinpoint why the problem exists in the first place, as "" seems to be a valid portal name. [1] - https://www.postgresql.org/docs/11/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY
Previous to this change, if you tried to issue a `SET` command, finagle-postgres would raise an exception telling no completion command is known for tag `SET`. This patch implements such a response from server. `SET` commands are needed for sending runtime settings to postgres or when trying to set the current transaction isolation level. See: zio/zio-quill#29 (comment)
scala-steward
force-pushed
the
update/shapeless-2.3.10
branch
from
August 11, 2023 15:12
12d988a
to
937e117
Compare
Signed-off-by: Iván Molina Rebolledo <ivanmolinarebolledo@gmail.com>
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.
Updates com.chuusai:shapeless from 2.3.3 to 2.3.10.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a
.scala-steward.conf
file.Have a fantastic day writing Scala!
Adjust future updates
Add this to your
.scala-steward.conf
file to ignore future updates of this dependency:Or, add this to slow down future updates of this dependency:
labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1