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

Creating a note on observed data crashes the website #4153

Closed
Shaneosaure opened this issue Aug 24, 2023 · 0 comments · Fixed by #4159
Closed

Creating a note on observed data crashes the website #4153

Shaneosaure opened this issue Aug 24, 2023 · 0 comments · Fixed by #4159
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)

Comments

@Shaneosaure
Copy link

Description

When creating a note on observed datas, the observed data loose its name value and crash the whole tab.

Environment

  1. OS (where OpenCTI server runs): Demo and Kubernetes v1.27
  2. OpenCTI version: OpenCTI 5.9.6
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to observed data
  2. Create a note on the observed data
  3. Refresh the page

Expected Output

Seeing the note on the observed data like so :
Capture d'écran 2023-08-24 083441

Actual Output

The whole tab of observed data crashes :
Capture d'écran 2023-08-24 083711

The whole data/entities tab also crashes:
Capture d'écran 2023-08-24 083800

Error output:

["Error: Cannot return null for non-nullable field ObservedData.name."

Additional information

  • Only solution so far is to delete the note, wait for the background task to end, and then refresh the page.
  • Creating a note on other SDO doesn't create such a bug
@Shaneosaure Shaneosaure added the bug use for describing something not working as expected label Aug 24, 2023
@yassine-ouaamou yassine-ouaamou self-assigned this Aug 24, 2023
@SamuelHassine SamuelHassine added this to the Release 5.10.0 milestone Aug 24, 2023
@RomuDeuxfois RomuDeuxfois added the solved use to identify issue that has been solved (must be linked to the solving PR) label Aug 25, 2023
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.

5 participants