update_event() method resulting in gateway timeouts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 491
- Forks
- 290
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 3
Description
MISP version: 2.5.19
PyMISP version: 2.5.17
I have a MISP instance connected to multiple remote instances, where I push events to them.
I retrieve a pythonified object of an event, called e. I change the last_seen value of an attribute of this event, and keep the Published key of the event e as True. When I call the misp.update_event(e) method, after some period of time, I receive a gateway timeout message while trying to push the event to a remote instance. Sometimes it happens with the third remote instance, sometimes with the fifth... it doesn't have a pattern. It's not always the same remote instance.
If I change the Published key of the event e to False, call the misp.update_event(e) method, and finally call the misp.publish(e) method, everything works fine!
Is this behavior expected?
Thank you very much!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the update_event(e) and publish(e) entry points and reproduce the case with Published set to True against multiple remote instances. Trace where the gateway timeout occurs and compare it with the False-then-publish workflow. Done means the expected behavior is established and the timeout behavior is addressed or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100