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.

Sign up for GitHub

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

Jump to bottom

"Simulation results" chart in a scenario is not accurate #1997

Closed
jborozco opened this issue Dec 5, 2024 · 1 comment · Fixed by #1995
Closed

"Simulation results" chart in a scenario is not accurate #1997

jborozco opened this issue Dec 5, 2024 · 1 comment · Fixed by #1995
Assignees
@isselparra
Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature solved The issue has been solved
Milestone
Release 1.10.0

Comments

@jborozco
Copy link

jborozco commented Dec 5, 2024

Description

in
https://testing.obas.staging.filigran.io/admin/scenarios/f1dfa3c8-dbb2-4fdf-9997-8467ff97238a?query=cGFnZT0wJnNpemU9MjAmc29ydHMlNUIwJTVEJTVCcHJvcGVydHklNUQ9ZXhlcmNpc2Vfc3RhcnRfZGF0ZSZrZXk9c2NlbmFyaW8tZjFkZmEzYzgtZGJiMi00ZmRmLTk5OTctODQ2N2ZmOTcyMzhhLXNpbXVsYXRpb25z
the chart are showing 100% of success which is not accurate with the simulation:

Image

Image

Environment

  1. OS (where OpenBAS server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenBAS version: { e.g. OpenBAS 1.0.2 }
  3. OpenBAS 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)
@jborozco jborozco 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 Dec 5, 2024
@jborozco jborozco added this to the Bugs backlog milestone Dec 5, 2024
@jborozco jborozco added the regression Label to identify the bug as a regression of previously working feature label Dec 5, 2024
@jborozco jborozco mentioned this issue Dec 5, 2024
Closed
@savacano28 savacano28 linked a pull request Dec 13, 2024 that will close this issue
[backend/frontend] Ability to see 100 simulations in the overview of a scenario in 0.5 seconds #1995
Merged
5 tasks
@savacano28 savacano28 added the solved The issue has been solved label Dec 13, 2024
@savacano28
Copy link
Contributor

Solved by Issel. PR: #1995

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@isselparra isselparra

Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature solved The issue has been solved
Projects
None yet
Milestone
Release 1.10.0
3 participants
@savacano28 @isselparra @jborozco