search

nens / servicedesk-issue-only

This repository will be used primarily by the service desk to report issues which will then be moved by the teamleads
0 stars 0 forks source link

[3Di]: Error 404 when download dialog opens (basic, arrival and damage from Lizard) (production) #90

Open GeOdin opened 2 years ago

GeOdin commented 2 years ago

Contact Details

No response

Topdesk URL (API)

No response

Incident Type

Error

What priority should we assign to this submission?

None

3Di component

Livesite

What happened?

I could not save my raw results on the live site. I expected to be able to save the raw results when closing the model and choosing to save the results.

How to Reproduce?

I opened the v2_bergermeer_with_grndwtr #111 (revision 111) on the 3di live site (3di.live) I added 1 pump (standard pump) and 1 discharge (standard discharge) I let the model run for 6 seconds I choose stop simulation in the user menu Open the dev tools now (F12) I choose save results in the dialog that opens I could not save the (raw) results The devtools show 404 errors of Lizard

What did you expect and what was the actual result?

I could not save my raw results on the live site. I expected to be able to save the raw results when closing the model and choosing to save the results.

Nothing happened. In the devtools, you could see a 404 error of Lizard for arrival, damage and basic.

GET https://api.3di.live/v3/simulations/89180/results/post_processing/lizard/basic/ 404 GET https://api.3di.live/v3/simulations/89180/results/post_processing/lizard/arrival/ 404 GET https://api.3di.live/v3/simulations/89180/results/post_processing/lizard/damage/ 404

Add screenshots, video's etc

20220825 - 3di live - lizard 404 error basic arrival damage when choosing to save results and dialog opens

Relevant log output

## Short version:

GET https://api.3di.live/v3/simulations/89180/results/post_processing/lizard/basic/ 404 
GET https://api.3di.live/v3/simulations/89180/results/post_processing/lizard/arrival/ 404 
GET https://api.3di.live/v3/simulations/89180/results/post_processing/lizard/damage/ 404 

## Long version:

runtime.js:97          GET https://api.3di.live/v3/simulations/89181/results/post_processing/lizard/basic/ 404
(anonymous) @ runtime.js:97
(anonymous) @ runtime.js:62
(anonymous) @ runtime.js:43
(anonymous) @ runtime.js:37
a @ runtime.js:33
fetchApi @ runtime.js:78
(anonymous) @ runtime.js:157
(anonymous) @ runtime.js:62
(anonymous) @ runtime.js:43
(anonymous) @ runtime.js:37
a @ runtime.js:33
t.request @ runtime.js:151
(anonymous) @ V3Api.js:15575
(anonymous) @ V3Api.js:54
(anonymous) @ V3Api.js:35
(anonymous) @ V3Api.js:29
i @ V3Api.js:25
e.simulationsResultsPostProcessingLizardBasicListRaw @ V3Api.js:15556
(anonymous) @ V3Api.js:15596
(anonymous) @ V3Api.js:54
(anonymous) @ V3Api.js:35
(anonymous) @ V3Api.js:29
i @ V3Api.js:25
e.simulationsResultsPostProcessingLizardBasicList @ V3Api.js:15592
(anonymous) @ ExportMenu.tsx:104
Fl @ react-dom.production.min.js:262
e.unstable_runWithPriority @ scheduler.production.min.js:18
Hi @ react-dom.production.min.js:122
Nl @ react-dom.production.min.js:261
(anonymous) @ react-dom.production.min.js:261
z @ scheduler.production.min.js:16
b.port1.onmessage @ scheduler.production.min.js:12
runtime.js:97          GET https://api.3di.live/v3/simulations/89181/results/post_processing/lizard/damage/ 404
(anonymous) @ runtime.js:97
(anonymous) @ runtime.js:62
(anonymous) @ runtime.js:43
(anonymous) @ runtime.js:37
a @ runtime.js:33
fetchApi @ runtime.js:78
(anonymous) @ runtime.js:157
(anonymous) @ runtime.js:62
(anonymous) @ runtime.js:43
(anonymous) @ runtime.js:37
a @ runtime.js:33
t.request @ runtime.js:151
(anonymous) @ V3Api.js:15725
(anonymous) @ V3Api.js:54
(anonymous) @ V3Api.js:35
(anonymous) @ V3Api.js:29
i @ V3Api.js:25
e.simulationsResultsPostProcessingLizardDamageListRaw @ V3Api.js:15706
(anonymous) @ V3Api.js:15746
(anonymous) @ V3Api.js:54
(anonymous) @ V3Api.js:35
(anonymous) @ V3Api.js:29
i @ V3Api.js:25
e.simulationsResultsPostProcessingLizardDamageList @ V3Api.js:15742
(anonymous) @ ExportMenu.tsx:127
Fl @ react-dom.production.min.js:262
e.unstable_runWithPriority @ scheduler.production.min.js:18
Hi @ react-dom.production.min.js:122
Nl @ react-dom.production.min.js:261
(anonymous) @ react-dom.production.min.js:261
z @ scheduler.production.min.js:16
b.port1.onmessage @ scheduler.production.min.js:12
runtime.js:97          GET https://api.3di.live/v3/simulations/89181/results/post_processing/lizard/arrival/ 404

Additional info

Good luck! :)

GeOdin commented 2 years ago

Note: this is the rest of the relevant log output (the complete log output for the arrival 404)

GET https://api.3di.live/v3/simulations/89181/results/post_processing/lizard/arrival/ 404
(anonymous) @ runtime.js:97
(anonymous) @ runtime.js:62
(anonymous) @ runtime.js:43
(anonymous) @ runtime.js:37
a @ runtime.js:33
fetchApi @ runtime.js:78
(anonymous) @ runtime.js:157
(anonymous) @ runtime.js:62
(anonymous) @ runtime.js:43
(anonymous) @ runtime.js:37
a @ runtime.js:33
t.request @ runtime.js:151
(anonymous) @ V3Api.js:15425
(anonymous) @ V3Api.js:54
(anonymous) @ V3Api.js:35
(anonymous) @ V3Api.js:29
i @ V3Api.js:25
e.simulationsResultsPostProcessingLizardArrivalListRaw @ V3Api.js:15406
(anonymous) @ V3Api.js:15446
(anonymous) @ V3Api.js:54
(anonymous) @ V3Api.js:35
(anonymous) @ V3Api.js:29
i @ V3Api.js:25
e.simulationsResultsPostProcessingLizardArrivalList @ V3Api.js:15442
(anonymous) @ ExportMenu.tsx:116
Fl @ react-dom.production.min.js:262
e.unstable_runWithPriority @ scheduler.production.min.js:18
Hi @ react-dom.production.min.js:122
Nl @ react-dom.production.min.js:261
(anonymous) @ react-dom.production.min.js:261
z @ scheduler.production.min.js:16
b.port1.onmessage @ scheduler.production.min.js:12
GeOdin commented 2 years ago

Note: it is possible to download the results, even though the 404 errors still occur. I made a mistake of not pressing the save button in the save dialog. I updated the priority to None (to be determined), because this makes this ticket a less higher prio (I think).

Kind regards

Kind regards

Patrick-Nijman commented 2 years ago

404 errors occur before even choosing to download results to HD or Lizard. I think this is a remnant which needs to be cleared out of good practice.