-
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(rules): rule application occurs within DB transaction to ensure cursor is not closed prematurely #246
Conversation
/build_test |
Workflow started at 1/18/2024, 4:20:42 PM. View Actions Run. |
CI build and push: All tests pass ✅ |
1 similar comment
CI build and push: All tests pass ✅ |
692f9a6
to
e88721a
Compare
…ursor is not closed prematurely
e88721a
to
80e7374
Compare
/build_test |
Workflow started at 1/19/2024, 3:13:06 PM. View Actions Run. |
CI build and push: All tests pass ✅ |
1 similar comment
CI build and push: All tests pass ✅ |
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
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: #245
Description of the change:
Annotate method with
@Transactional
to ensure the database cursor/connection is not prematurely closed.Motivation for the change:
See #245
How to manually test:
See #245
Also try:
Upload this rule definition and enable it. Recordings should be started within a few seconds, and then every 15 seconds afterward should be archived, and once there are 3 copies of each, the oldest copies should start rolling over and getting deleted.