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

[3Di]: Running model after DEM edit crashes live site (staging) #158

Open
GeOdin opened this issue Mar 31, 2023 · 1 comment
Open

[3Di]: Running model after DEM edit crashes live site (staging) #158

GeOdin opened this issue Mar 31, 2023 · 1 comment
Assignees
Labels
⏰ Priority: 2. High The issue will be seen by most users. 🧪Testing: Found during testing 💡 Type: Bug The issue documents broken, incorrect, or confusing behavior. Always accompanied by a Severity label

Comments

@GeOdin
Copy link

GeOdin commented Mar 31, 2023

Contact Details

No response

Topdesk URL (API)

No response

Incident Type

Error

What priority should we assign to this submission?

Prio2 Urgent

3Di component

Livesite

What happened?

When I created a DEM edit before the model runs and then press play, the live site crashes (on Chrome).
When I create a DEM edit when the model was already running, it also crashed the live site.

How to Reproduce?

Open the live site staging on Chrome https://www.staging.3di.live/
Select a model (eg v2_bergermeer_with_grndwtr #115 with with_grndwtr template
Optional: open the layers menu (bottom left) and show the DEM (height/ elevation map)
Create a DEM edit
Press play

What did you expect and what was the actual result?

I did not expect that running the model after creating a DEM edit would crash the model.

Add screenshots, video's etc

No response

Relevant log output

No response

Additional info

Good luck! :)

@GeOdin GeOdin added 🧪Testing: Found during testing 💡 Type: Bug The issue documents broken, incorrect, or confusing behavior. Always accompanied by a Severity label ⏰ Priority: 2. High The issue will be seen by most users. labels Mar 31, 2023
@GeOdin
Copy link
Author

GeOdin commented Mar 31, 2023

I set the priority to high, bacause I think this needs to be fixed for the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⏰ Priority: 2. High The issue will be seen by most users. 🧪Testing: Found during testing 💡 Type: Bug The issue documents broken, incorrect, or confusing behavior. Always accompanied by a Severity label
Projects
None yet
Development

No branches or pull requests

2 participants