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
chore(deps,test): integrate engine iTX error messages changes #16382
Merged
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
aqrln
requested review from
a team and
SevInf
and removed request for
a team
November 21, 2022 16:53
This comment was marked as outdated.
This comment was marked as outdated.
aqrln
force-pushed
the
integrate-itx-errors
branch
from
November 21, 2022 20:03
526b0ca
to
0d226f6
Compare
SevInf
approved these changes
Nov 22, 2022
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.
LGTM after engine changes are done
aqrln
added a commit
to prisma/prisma-engines
that referenced
this pull request
Nov 23, 2022
Make the error messages for closed transactions more detailed, add extra context about the transaction timeout. Before: - `Transaction API error: Transaction already closed: A query/commit/rollback cannot be executed on a closed transaction..` (also note the double "." at the end) Now: - `Transaction API error: Transaction already closed: A query/commit/rollback cannot be executed on a committed transaction.` - `Transaction API error: Transaction already closed: A query/commit/rollback cannot be executed on a transaction that was rolled back.` - `Transaction API error: Transaction already closed: A query/commit/rollback cannot be executed on an expired transaction. The timeout for this transaction was X ms, however Y ms passed since the start of the transaction. Consider increasing the interactive transaction timeout or doing less work in the transaction.` Additionally, the "Transaction not found error" is now also more verbose, ref: https://www.notion.so/disconnect-with-iTX-f3cfee3ff4924e40aa90aadb2454e9fa?d=3bd7c7103b02461bbfe414a978a994c1#547ab127682b41898c87bdd5c841c0bf Also contains minor cleanup things related to iTX: * Remove the unused `CachedTx::Aborted` variant * Remove references to an obsolete env var that doesn't exist since #3028 from comments and `.envrc` Client PR: prisma/prisma#16382 Closes: prisma/prisma#13713 Ref: prisma/prisma#16050 Ref: #3028
aqrln
force-pushed
the
integrate-itx-errors
branch
from
November 23, 2022 13:26
0d226f6
to
807389b
Compare
aqrln
changed the title
test(client): integrate engine iTX error messages changes
chore: integrate engine iTX error messages changes
Nov 23, 2022
aqrln
changed the title
chore: integrate engine iTX error messages changes
chore(deps,test): integrate engine iTX error messages changes
Nov 23, 2022
jkomyno
pushed a commit
that referenced
this pull request
Dec 21, 2022
jkomyno
pushed a commit
that referenced
this pull request
Dec 21, 2022
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.
Ref: prisma/prisma-engines#3391