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

[Intel471 V1] Issue when upgrading Titan library #3206

Closed
helene-nguyen opened this issue Jan 2, 2025 · 0 comments · Fixed by #3207
Closed

[Intel471 V1] Issue when upgrading Titan library #3206

helene-nguyen opened this issue Jan 2, 2025 · 0 comments · Fixed by #3207
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@helene-nguyen
Copy link
Member

Description

Issue following the upgrade of Titan library from 1.20.0.4 to 1.20.0.6

Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/apscheduler/executors/base.py", line 131, in run_job retval = job.func(*job.args, **job.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/opencti-intel471/intel471/streams/common.py", line 74, in run for bundle in self.get_bundles(): ^^^^^^^^^^^^^^^^^^ File "/opt/opencti-intel471/intel471/streams/common.py", line 109, in get_bundles STIXMapperSettings( TypeError: STIXMapperSettings.__new__() got an unexpected keyword argument 'report_attachments_opencti'

Due to these following changes:

intel471/titan-client-python@de02793#diff-96dbc385c41ca447d6fdd73f25608d9ed1a1c953fe8e9ffe027ffe414a6e49e8R15

Image

@helene-nguyen helene-nguyen added the bug use for describing something not working as expected label Jan 2, 2025
@helene-nguyen helene-nguyen self-assigned this Jan 2, 2025
@helene-nguyen helene-nguyen linked a pull request Jan 2, 2025 that will close this issue
4 tasks
@helene-nguyen helene-nguyen added this to the Release 6.4.6 milestone Jan 2, 2025
@helene-nguyen helene-nguyen added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant