-
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 archiving and re-activation bugfixes #518
Conversation
/build_test |
Workflow started at 6/13/2024, 11:06:57 AM. View Actions Run. |
CI build and push: All tests pass ✅ (JDK17) |
/build_test |
Workflow started at 6/13/2024, 11:20:08 AM. View Actions Run. |
No OpenAPI schema changes detected. |
No GraphQL schema changes detected. |
CI build and push: All tests pass ✅ (JDK17) |
/build_test |
Workflow started at 6/13/2024, 2:57:40 PM. 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.
Works as described
@Mergifyio backport cryostat-v3.0 |
✅ Backports have been created
|
* fix(rules): rule archiving and re-activation bugfixes * refactor * blocking * activate concurrently * cancel job when target disappears * fixup! cancel job when target disappears * apply existing rules to newly appearing targets (cherry picked from commit 233df2a)
…#519) fix(rules): rule archiving and re-activation bugfixes (#518) * fix(rules): rule archiving and re-activation bugfixes * refactor * blocking * activate concurrently * cancel job when target disappears * fixup! cancel job when target disappears * apply existing rules to newly appearing targets (cherry picked from commit 233df2a) Co-authored-by: Andrew Azores <me@andrewazor.es>
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: #517
Description of the change:
Fixes up some issues that arose due to previous refactorings, where collections were improperly modified during traversal, or methods went from blocking operations to returning
Uni
s which went ignored, or active recordings were improperly left running, or duplicate target definitions were not de-duplicated by JVM ID and thus were acted on multiple times.How to manually test:
./smoketest.bash -Ot
clean
option checked and ensure recordings are stopped