-
Notifications
You must be signed in to change notification settings - Fork 205
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
Relax SQL exception constraints in ReadOnlySqlLedger #7675
Conversation
af4af7d
to
c7d03c9
Compare
c7d03c9
to
5bff05d
Compare
changelog_begin changelog_end
5bff05d
to
b979abd
Compare
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.
On second thought, can you double-check HikariJdbcConnectionProvider.scala
?
Also, I think some unit tests are failing https://dev.azure.com/digitalasset/daml/_build/results?buildId=57951&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=f58be928-45a1-58e7-c1ad-04869565b3f4&l=4481
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
It seems that the failure is occasional and not related (a ticket is already open for this #7521) |
Relax SQL exception constraints in
ReadOnlySqlLedger
This was motivated by the fact that PostgreSQL errors do not inherit from
java.sql.SQLNonTransientException
. We do not want to rely on database implementations throwing specific errors.Pull Request Checklist
CHANGELOG_BEGIN
andCHANGELOG_END
tagsNOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines run
totrigger the build.