Skip to content

Conversation

@samuelFain
Copy link
Contributor

@samuelFain samuelFain commented Nov 19, 2025

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

relates: XSUP-56277

Description

A few sentences describing the overall goals of the pull request's commits.

Must have

  • Tests
  • Documentation

- Implemented IntegrationContextManager for thread-safe integration context operations
- Added ThreadPoolExecutor-based parallel fetching
- Implemented coordinated access token refresh to prevent token collisions
- Added enable_multithreading configuration parameter
- Alerts processed sequentially, Activities/Devices fetched in parallel
- Added comprehensive logging with worker identification
- Includes full test coverage for multithreading scenarios
- SIM102: Combined nested if statements in refresh_access_token
- E501: Split long debug log line in parallel processing
- SIM117: Combined nested with statements in test
- F841: Removed unused mock_set variable in test
@content-bot
Copy link
Collaborator

⚠️ The PR is missing the ready-for-pipeline-running label. Please add the label when the PR is ready in order to proceed.

@github-actions
Copy link

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/Armis/Integrations/ArmisEventCollector
   ArmisEventCollector.py3736083%117–120, 128–129, 159–161, 174, 198, 201, 244–246, 305, 347–353, 363–367, 369, 387–388, 390–391, 393, 430, 432, 663–665, 707–708, 729, 817–819, 849, 877–880, 882–886, 888–889, 891–892, 937
TOTAL3736083% 

Tests Skipped Failures Errors Time
37 0 💤 0 ❌ 0 🔥 2.628s ⏱️

@content-bot
Copy link
Collaborator

Validate summary
The following errors were thrown as a part of this pr: PA114, DO106, RN106.
The following errors cannot be ignored: PA114, DO106, RN106.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: PA114, DO106, RN106.

Verdict: PR can be force merged from validate perspective? ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants