-
Notifications
You must be signed in to change notification settings - Fork 10
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
fix(db): correct use of Transactional annotation #415
Conversation
9f8ceed
to
2ef8be7
Compare
/build_test |
Workflow started at 4/29/2024, 10:17:20 AM. View Actions Run. |
No GraphQL schema changes detected. |
No OpenAPI schema changes detected. |
CI build and push: All tests pass ✅ (JDK17) |
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.
Looks good to me.
/build_test |
Workflow started at 5/8/2024, 11:38:18 AM. View Actions Run. |
No GraphQL schema changes detected. |
No OpenAPI schema changes detected. |
CI build and push: All tests pass ✅ (JDK17) |
Welcome to Cryostat3! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/main
Fixes: #405
Fixes: #440
Description of the change:
Removes useless instances of
Transactional
annotation and replaces them withQuarkusTransaction.joiningExisting()
invocations where applicable.Motivation for the change:
Ensures operations actually occur in a transactional context as expected
How to manually test: