fix: avoid creating SOAR session on close - #260
Merged
dandye merged 1 commit intoAug 29, 2026
Conversation
Contributor
Author
|
This is ready for review. Closing a SOAR session no longer creates a new session, and the visible checks are green. |
dandye
approved these changes
Aug 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HttpClient.close()should only close an existing aiohttp session. Calling_get_session()insideclose()creates a new session just to close it, which gives cleanup an unnecessary side effect.This skips the close call when no session has been created yet.
Tests:
python3 -m py_compile server/secops-soar/secops_soar_mcp/http_client.pyPYTHONPATH=/tmp/mcp-security-http-deps:server/secops-soar python3 - <<'PY' ...smoke test for closing a client before any request creates a sessiongit diff --check