Instead of grabbing the actual dataset_id from the simulation dataset, it is treating the simulation_dataset_id as dataset_id. This causes problems when the dataset_id and simulation_dataset_id fall out of sync (for example, via adding external datasets). Once this desync happens, the UI will either fail to get any results for a sim run, or will fetch incorrect results.
Reproduction
Create a plan
Add an external dataset via the API
Simulate the plan
Example video on a localhost venue where the desync was caused by running the external dataset E2E tests in Aerie core:
Checked for duplicates
No - I haven't checked
Is this a regression?
Yes - This worked in a previous version
Version
2.1.0
Describe the bug
This bug was likely introduced in #1017, L305 of
+page.svelete
Instead of grabbing the actual
dataset_id
from the simulation dataset, it is treating thesimulation_dataset_id
asdataset_id
. This causes problems when thedataset_id
andsimulation_dataset_id
fall out of sync (for example, via adding external datasets). Once this desync happens, the UI will either fail to get any results for a sim run, or will fetch incorrect results.Reproduction
Example video on a localhost venue where the desync was caused by running the external dataset E2E tests in Aerie core:
https://github.com/NASA-AMMOS/aerie-ui/assets/62574120/b2100b6d-c6c7-4792-a27d-9f9d9ca30f68
Database entry for this request. Notice how the dataset id does not equal the request's id:
Query that the UI made to get the spans. Notice that it used 107, the request id, instead of 133, the dataset id
Logs
No response
System Info
Severity
Major