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

Update shapeless to 2.3.10 #291

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

scala-steward
Copy link
Contributor

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:

updates.ignore = [ { groupId = "com.chuusai", artifactId = "shapeless" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.chuusai", artifactId = "shapeless" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

davoclavo and others added 5 commits June 30, 2020 00:36
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 scala-steward force-pushed the update/shapeless-2.3.10 branch from 12d988a to 937e117 Compare August 11, 2023 15:12
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants