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

An infinite update loop can happen when two instances listen to each other streams #9824

Closed
JeremyCloarec opened this issue Feb 4, 2025 · 0 comments · Fixed by #9791
Closed
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)

Comments

@JeremyCloarec
Copy link
Contributor

Description

When two platforms are interconnected with two streams on each side, a scenario can happen where updates are sent in an infinite loop between the instances.
This can occur when one of the platform makes two updates in a short amount of time.

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)

@JeremyCloarec JeremyCloarec added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 4, 2025
@JeremyCloarec JeremyCloarec removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 4, 2025
JeremyCloarec added a commit that referenced this issue Feb 4, 2025
@JeremyCloarec JeremyCloarec added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 4, 2025
@labo-flg labo-flg added this to the Release 6.4.11 milestone Feb 4, 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
2 participants