MISP / MISP/PyMISP

I don't want it to print 'stderr' on the Output

Open
#979 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
491
Forks
290
Avg merge
2d 8h
Merged PRs (30d)
3

Description

Hi all,
I use PYMISP().add_attribute() to add multiple IOCs to MISP. Here, if there is duplicate state, I see "Stderr: Something went wrong (403): {'saved': False, 'name': 'Could not add Attribute', 'message': 'Could not add Attribute', 'url': '/attributes/add', 'errors': {'value': ['A similar attribute already exists for this event.']}}" in the output. How can I prevent this? So I don't want stderr to be written to the output even if it is duplicate.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at PYMISP().add_attribute() and trace how duplicate-attribute responses are written to stderr. Check whether the client exposes an existing way to control this output. Done means duplicate additions no longer print stderr to the caller's output while the duplicate response remains available.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.