Skip to content

Fix / XSUP-78657 / Anomali threat intel feed push by streaming - #46232

Open
MosheEichler wants to merge 14 commits into
masterfrom
fix/XSUP-78657-anomali-threatstream-feed-oom
Open

MosheEichler wants to merge 14 commits into
masterfrom
fix/XSUP-78657-anomali-threatstream-feed-oom

Conversation

@MosheEichler

Copy link
Copy Markdown
Contributor

Status

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

Related Issues

https://jira-dc.paloaltonetworks.com/browse/XSUP-78657

Description

Improvement: Migrated the indicator creation process to a streaming mechanism.

Must have

  • Tests
  • Documentation

@MosheEichler MosheEichler added release-notes-only Indicates that this pull request has ONLY release notes to review for documentation process ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. labels Oct 13, 2026
@content-bot

Copy link
Copy Markdown
Contributor

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @marketplace-ai-reviewer start review - Initiate a full AI code review
  • @marketplace-ai-reviewer re-review - Incremental review for new commits

@marketplace-ai-reviewer marketplace-ai-reviewer removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Oct 13, 2026
@marketplace-ai-reviewer

Copy link
Copy Markdown
Contributor

🤖 Analysis started. Please wait for results...

@github-actions

github-actions Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/AnomaliThreatStreamFeed/Integrations/AnomaliThreatStreamFeed
   AnomaliThreatStreamFeed.py2523984%86–89, 101, 164–165, 193, 210–212, 364, 455, 469–470, 506, 532, 571, 573, 700–701, 703, 706–708, 710–711, 718, 720, 722–723, 725, 728–730, 736, 738–740
TOTAL2523984% 

Tests Skipped Failures Errors Time
51 0 💤 0 ❌ 0 🔥 3.988s ⏱️

@marketplace-ai-reviewer

Copy link
Copy Markdown
Contributor
🤖 AI Review Disclaimer

This review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause.

@marketplace-ai-reviewer marketplace-ai-reviewer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution to the Anomali ThreatStream Feed pack! I've reviewed the PR and found a critical issue regarding potential data loss, along with a few minor metadata fixes.

Most importantly, please move the indicator creation logic (parse_and_push) outside of the try...except block to prevent silent failures from incorrectly updating the last_run timestamp. Additionally, ensure that your exception logs include tracebacks, and update the pack metadata to include the missing created key and vendor keyword.

Great work so far, looking forward to the updates!

Additionally, please address the following file-level notes:

  • Packs/AnomaliThreatStreamFeed/pack_metadata.json: - The mandatory key created is missing from the pack metadata.
  • The vendor name is missing from the keywords field.

@DeanArbel, @MosheEichler please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

@MosheEichler MosheEichler added the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Oct 13, 2026
@marketplace-ai-reviewer marketplace-ai-reviewer removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Oct 13, 2026
@marketplace-ai-reviewer

Copy link
Copy Markdown
Contributor

🤖 Analysis started. Please wait for results...

@marketplace-ai-reviewer

Copy link
Copy Markdown
Contributor
🤖 AI Review Disclaimer

This review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause.

@marketplace-ai-reviewer marketplace-ai-reviewer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔄 Re-reviewing updates...

Important

To maintain review integrity, threads marked as Resolved without accompanying changes or explanations will be automatically unresolved for further verification.

Thank you for your contribution! Re-reviewed your PR, No new issues found. Great work! 👍
Please check the previous comments to ensure all feedback has been resolved.

@marketplace-ai-reviewer, @DeanArbel, @MosheEichler please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

@content-bot

This comment has been minimized.

@content-bot

This comment has been minimized.

@MosheEichler

MosheEichler commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor Author

@content-bot

This comment has been minimized.

@content-bot

This comment has been minimized.

MosheEichler and others added 3 commits October 21, 2026 11:42
- Clarified additional info for 'Bypass exclusion list' and 'Tags' parameters in YAML and README.
- Added details to release notes for new integration parameters.
@content-bot

This comment has been minimized.

@MosheEichler
MosheEichler marked this pull request as ready for review October 22, 2026 12:23
@MosheEichler
MosheEichler enabled auto-merge (squash) October 22, 2026 12:23
@content-bot

This comment has been minimized.

@MosheEichler MosheEichler added the ForceMerge Forcing the merge of the PR despite the build status label Oct 22, 2026
@content-bot

Copy link
Copy Markdown
Contributor

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

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

@content-bot

Copy link
Copy Markdown
Contributor

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: failed
Report ID: 5737f44e11f19381

📋 Triage Report
💡 Resolutions are available in the full report.

⚠️ AI-generated triage. Validate before acting.

This branch has not been deployed

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

Labels

connectus-approved docs-approved ForceMerge Forcing the merge of the PR despite the build status ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines release-notes-only Indicates that this pull request has ONLY release notes to review for documentation process supported-modules-approved

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants