Skip to content
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

[Silobreaker] Issue on first run of connector #3501

Closed
helene-nguyen opened this issue Feb 25, 2025 · 0 comments · Fixed by #3573
Closed

[Silobreaker] Issue on first run of connector #3501

helene-nguyen opened this issue Feb 25, 2025 · 0 comments · Fixed by #3573
Assignees
Labels
feature use for describing a new feature to develop improvement solved use to identify issue that has been solved (must be linked to the solving PR) to verify use to identified for Verified
Milestone

Comments

@helene-nguyen
Copy link
Member

Description

Issue on first run of connector

{"timestamp": "2025-02-15T18:26:11.279824Z", "level": "ERROR", "name": "Silobreaker Cyber Threat Intelligence", "message": "'Description'", "exc_info": "Traceback (most recent call last):\n File \"C:\\Users\\RomainGuignard\\IdeaProjects\\connectors\\external-import\\silobreaker\\src\\silobreaker.py\", line 700, in run\n self._process_lists(work_id, delta_days)\n File \"C:\\Users\\RomainGuignard\\IdeaProjects\\connectors\\external-import\\silobreaker\\src\\silobreaker.py\", line 668, in _process_lists\n self._import_documents(data[\"Description\"], work_id, delta_days)\n ~~~~^^^^^^^^^^^^^^^\nKeyError: 'Description'", "taskName": null}

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: { e.g. OpenCTI 1.0.2 }
  3. OpenCTI client: { e.g. frontend or python }
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. { e.g. Run ... }
  2. { e.g. Click ... }
  3. { e.g. Error ... }

Expected Output

Actual Output

Additional information

Screenshots (optional)

@helene-nguyen helene-nguyen added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team to verify use to identified for Verified labels Feb 25, 2025
@romain-filigran romain-filigran added improvement and removed bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 26, 2025
@romain-filigran romain-filigran added this to the To Verify Backlog milestone Feb 26, 2025
@Jipegien Jipegien removed this from the To Verify Backlog milestone Mar 3, 2025
@helene-nguyen helene-nguyen self-assigned this Mar 3, 2025
@helene-nguyen helene-nguyen linked a pull request Mar 6, 2025 that will close this issue
4 tasks
@SamuelHassine SamuelHassine added feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR) labels Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop improvement solved use to identify issue that has been solved (must be linked to the solving PR) to verify use to identified for Verified
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants