-
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(transaction): ensure transactions occur in correct context/thread #396
fix(transaction): ensure transactions occur in correct context/thread #396
Conversation
a4113a6
to
efb6679
Compare
/build_test |
This PR/issue depends on:
|
Workflow started at 4/23/2024, 2:41:20 PM. View Actions Run. |
No OpenAPI schema changes detected. |
No GraphQL schema changes detected. |
CI build and push: All tests pass ✅ (JDK17) |
efb6679
to
aff1c63
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.
looks good, just needs a rebase
/build_test |
Workflow started at 4/24/2024, 1:21:14 PM. View Actions Run. |
No GraphQL schema changes detected. |
No OpenAPI schema changes detected. |
aff1c63
to
629a0f0
Compare
CI build and push: All tests pass ✅ (JDK17) |
/build_test |
Workflow started at 4/24/2024, 1:33:09 PM. View Actions Run. |
No OpenAPI schema changes detected. |
No GraphQL 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: #389
Based on #342
Description of the change:
Blocking
andTransactional
annotations are applied correctly in GraphQL API entrypoints and HTTP API entrypointsMotivation for the change:
This change is helpful because users may want to...
How to manually test: