You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
update_event() method resulting in gateway timeouts #1347
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!
Hmm, it shouldn't be, I thought we moved the publishing to a separate process everywhere, looks like we haven't though. Thanks for the heads up, definitely something for us to fix (on a MISP core level that is, pymisp isn't at fault here).
Activity
iglocska commentedon Aug 26, 2025
Hmm, it shouldn't be, I thought we moved the publishing to a separate process everywhere, looks like we haven't though. Thanks for the heads up, definitely something for us to fix (on a MISP core level that is, pymisp isn't at fault here).