-
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(recordings): use safe recording close on cleanup #763
fix(recordings): use safe recording close on cleanup #763
Conversation
/build_test |
Workflow started at 1/2/2025, 10:55:42 AM. View Actions Run. |
No OpenAPI schema changes detected. |
No GraphQL schema changes detected. |
CI build and push: All tests pass ✅ |
b186263
to
161a626
Compare
/build_test |
Workflow started at 1/10/2025, 9:07:59 AM. View Actions Run. |
No OpenAPI schema changes detected. |
No GraphQL schema changes detected. |
CI build and push: All tests pass ✅ |
Welcome to Cryostat! 👋
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: #760
Description of the change:
safeCloseRecording
method in two places where it wasn't before. Without this, any target connection failure would throw an exception and cause an early return from the callsites, which could lead to unexpected behaviour like orphaned resources left behind. This is the real fix.INFO
level toALL
in all cases, but I found that this actually interfered with the smoketest operation at times due to the extremely high verbosity - actions like archiving recordings actually saw a performance degradation because every byte written out by Cryostat would be logged, which drastically slowed the I/O and could cause operations to time out.Motivation for the change:
This change is helpful because users may want to...
How to manually test:
./smoketest.bash -Ot
(pass-v
one or two times to enable verbose logging)