Skip to content

Address transaction state edge cases - #447

Merged
inexorabletash merged 2 commits into
mainfrom
transaction-state-fixes
Apr 24, 2025
Merged

Address transaction state edge cases#447
inexorabletash merged 2 commits into
mainfrom
transaction-state-fixes

Conversation

@inexorabletash

@inexorabletash inexorabletash commented Apr 11, 2025

Copy link
Copy Markdown
Member
  • Clarify that only inactive transactions should auto-commit.

  • Fix upgrade steps to correctly handle aborted transactions.

Resolves #436


Preview | Diff

@inexorabletash

Copy link
Copy Markdown
Member Author

@stelar7 can you take a look?

* Clarify that only inactive transactions should auto-commit.

* Fix upgrade steps to correctly handle aborted transactions.

Resolves #436
@inexorabletash
inexorabletash force-pushed the transaction-state-fixes branch from fc928ae to 66fa597 Compare April 11, 2025 19:34

@stelar7 stelar7 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would like some more distinct steps that shows where/when the transaction should auto-commit, but this fixes the other part of the issue 👍

@SteveBeckerMSFT SteveBeckerMSFT left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay. Looks good to me. Thanks for fixing the extra brackets around my detached buffer change. Not sure how I missed that.

@inexorabletash
inexorabletash merged commit fe4a092 into main Apr 24, 2025
github-actions Bot added a commit that referenced this pull request Apr 24, 2025
SHA: fe4a092
Reason: push, by inexorabletash

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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.

Wait loop questions

3 participants