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

When adding a team with multiple players, it can lead to duplicate inserted in database which generate an error #1476

Closed
Dimfacion opened this issue Sep 18, 2024 · 0 comments
Assignees
Labels
bug use for describing something not working as expected solved The issue has been solved
Milestone

Comments

@Dimfacion
Copy link
Member

Description

When adding a team with multiple players, it can lead to duplicate inserted in database which generate an error.

Environment

  1. OS (where OpenBAS server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. } All
  2. OpenBAS version: { e.g. OpenBAS 1.0.2 } 1.6.1
  3. OpenBAS client: { e.g. frontend or python } Frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. { e.g. Run ... } Add a team with at least 1 player already existing and added to the scenario
  2. { e.g. Click ... } Import injects with that same team
  3. { e.g. Error ... } Error 409 ""A different object with the same identifier value was already associated with the session : [io.openbas.database.model.ScenarioTeamUser#ScenarioTeamUserId(scenarioId=xxx, teamId=xxx, userId=xxx)]"
    "

Expected Output

Import Sucessful

Actual Output

Import in error

Additional information

Screenshots (optional)

@Dimfacion Dimfacion added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels Sep 18, 2024
@RomuDeuxfois RomuDeuxfois added this to the Bugs backlog milestone Sep 19, 2024
@Dimfacion Dimfacion modified the milestones: Bugs backlog, Release 1.7.0 Sep 27, 2024
@Dimfacion Dimfacion added the solved The issue has been solved label Sep 27, 2024
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 The issue has been solved
Projects
None yet
Development

No branches or pull requests

2 participants